Page History

...

• 1. Identify a way to get the logs we need in the right format given the current implementation or...
  2. Identify what needs to be done/changed/re-configured to support current reporting needs and enable simple triaging of operational applications. 

Discussion items

• Jira
  server Earthdata Ticketing System columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 9a2ac141-7181-31f1-a247-ccbc66e20158 key NGAP-2296

• Doug noticed a new format in the logs coming from 1.1. Upon so, he noticed that all queries needed to be updated in order to meet the current metric reporting.
  • That's a bit of a beat down given that the hope was just to update sourcetypes and everything just works
  • This works for EDSC with some manual work.
  • The biggest concern for right now is triaging issues.
• Applications are just providing text. Splunk has some logic/black magic that identifies events as such and formats them certain ways.i
• Potential solution that needs to be researched - https://answers.splunk.com/answers/390219/how-to-parse-docker-logs-with-multiple-events-from.html
• Another link from Tim - https://github.com/moby/moby/issues/22920

...