...
- Update on Filebeat deployment.
- M3 (API freeze) debrief → LOG M3 API Freeze Checklist.
- Logging abstractions (Dave).
- Draft logging guide → ONAP Application Logging Guidelines v1.1.
- Continue discussion of tracing options:
- Implicitly logging ENTERING and EXITING in EELF (Lee).
- Generating InvocationID on the caller side (Dave).
- Persisting InvocationID and RequestID in cases like where execution may be deferred (e.g. BPMN).
- Engaging with the Documentation team.
Minutes:
- As above.
- Tentative agreement on InvocationID + Markers (details in logging guidlines).
- EELF ownership and contributions.
- Luke on Annual Leave next week.
Actions:
- Survey logging abstractions based on EELF and SLF4J. (Luke, Dave).
- Review and improve logging guidelines draft (everyone!)
- Find the right forum for discussing guidelines (Michael) - https://lists.onap.org/pipermail/onap-discuss/2017-September/
- Open source coordination for EELF - External Open Source Community Coordination
- Contact the ONAP Documentation team (Luke).
- Discuss Epic/Story status and merge status of OOM and LOG code
- We need to go through the backlog next week - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&projectKey=LOG&view=planning&selectedIssue=LOG-8