...
- 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 Wed to discussTue 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.
Rollover Actions
From last week
...
- 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
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-94 - AOP annotation support for Logging - check for existing code and raise (custom EELF annotations on top of Spring ?) -
Jira server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key LOG-95
...