Agenda:
- Update on OOM submissions in review (filebeat, config, ELK deployment yamls).
- Discuss logging spec of ONAP Application Logging Guidelines v1.1.
Minutes:
- Agree to finalize logging spec page edits and post to onap-discuss group for community involvement
- Need to raise epic for logging adjustments to align with spec / per project, raised Jiras for logging exceptions.
Actions:
- Cover off any tie in with the OPNFV project - OPNFV Integration
- 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) -
- 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
- Finish documenting logging locations, logging volume locations (OOM)
- Adjust OOM and ONAP on Kubernetes pages with Logging deployment info
- Create reference Kibana template (vFW distribution failure is a test case for requestID tracking for SDC/AAI/SO) - document on wiki
- Discuss whether we want to move with the HEAT version of the ELK stack
- 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