Agenda

R1 Release Checklist (yesterday)

Sign off on Luke's guidelines example from last meeting.

Go over new epics/jiras

LOG-95 - Getting issue details... STATUS

LOG-94 - Getting issue details... STATUS

Logging Guidelines

R1 Release Planning

Prepare for vote on Michael move to PTL proposal - Michael O'Brien PTL vote notes

Minutes

Discussed
cancel older jiras - recreate in B*
add cg doc section
need epic for guidelines
discuss invocation graphs and invocation id ~~requestid sequence diagram work - epic required~~
Need demo scenario to exercise the changes in the logging guidelines
need at least 2 components - epic standardize guidelines on 2 or more components (aai +)
ongoing logging format issue fixes
need to link oom log jiras until 2 step (guidelines= already being done in the cod + heat) - add LOG-45
need a design page on filebeat implemented - expand 45
RTD is the source of truth, the wiki is for pending changes for next release - join the Doc weekly meeting at 9amEDT Tue to discuss - developer focused means our wiki could still be the source of truth for present release.
ignore above -
Decision: the wiki is the source of truth for the guidelines - the RDT site will be periodic snapshots ONAP Application Logging Guidelines v1.1
Epic for rollout of guideline format to one of the components - aai? Later expanded to 2 or more for TX testing.

From last week

vote on ways to edit the guidelines next meet
vote meeting agenda flow - guide first, JIRA second ?
onap config is split - oom is working merging heat and oom
(oom config in oom project, heat it is in each project distributed across components)
discuss (raise epic) combining config - or raise a hierarchy (oparent?) - default version with specific overrides if required per project
need to discuss eelf consistency and MDC details for next meeting
LOG-85 discuss external mounts for /dockerdata-nfs shares and how to get it to work with emptyDir()
upfront arch discussion on implementation changes in the JIRA architecture page for epics in R2
small demo of functionality - proposals
f2f - discussions of logging exposure in the talks/hands-on/discussion-panels
vFirewall integration testing (daily) - always asking for logs in HEAT testing - we could address this in R2 either either through HEAT ELK or when OOM gets consumed in R2
2 logging related NPE bugs - we can fix these as well - we have 2 weeks

Epic for dual appenders (eelf, current) design issues, Resiliency/rotation changes, migration to single appender in the future - Mike
Epic for default configuration being applied
Finalize tabs vs pipes for R2 doc - vote on tue - 20171121 decision: Tabs/pipes - Send out to the Architecture team - onap-discuss - forward and review on next Tue Arch meeting
For human readable - differentiate between tabs and spaces?
Voting tabs=1 pipes=3 - push pipes to the community - get feedback by Nov 28
Discuss different line ending for indexing
Implementation (slf4j/eelf) is less of a concern over verifying that indexed content of the log format is standardized for consumers - however an additional API wrapper would benefit abstractONAP-component-wide changes over direct SLF4J calls.
Enumerate new ONAP projects as candidates for guideline enforcement.
Need volumetrics performance stats for end to end log emission all the way to ELK indexing/query - to be able to answer for more real time requestID tracking - like a DMaaP queue?
Committers have ideas about a 3rd appender to drop into the message queue DMaaP - a secondary, perhaps more performant view of the events.
Design Issue Epic for above LOG-94 - Getting issue details... STATUS
AOP annotation support for Logging - check for existing code and raise (custom EELF annotations on top of Spring ?) - LOG-95 - Getting issue details... STATUS

Attendees -