...

• Review guidelines in general
• Review line formats

• Comparison of line formats: from Luke

  Before:

  Code Block
  language text
  11/08-02:11:28.213|org.onap.example.component1.subcomponent1.LogbackTest|b88319fb-966e-4eb9-ad7f-a604da21c55a||main|||INFO||||||here's an info it has newlines and tabs

  After

  Code Block
  org.onap.example.component1.subcomponent1.LogbackTest 2017-11-07T15:11:28.213Z INFO here's an info\nit has newlines\tand tabs key1=value1, key2=value2 with space, RequestId=b88319fb-966e-4eb9-ad7f-a604da21c55a, key5=value5"with"quotes, key6=value5>with<chevrons, key3=value3\nwith\nnewlines, key4=value4\twith\ttabs main

• Introduce 2 new documentation contributors: Akanksha Khosla (OOM) , Anuj Kapoor (LOG)
• discuss doc work - todo
• discuss doc release notice work
• discuss carrier grade work in OOM -OOM for Carrier Grade Deployments around 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-109

• JIRA review - https://jira.onap.org/secure/RapidBoard.jspa?rapidView=53&view=planning&selectedIssue=LOG-85
• Triage log issues in other components, AAI, OOM - introduce Logging label
  

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key AAI-454

  , 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key OOM-403

• Discuss overall ONAP stability as it is affecting our log traceability - 

  Jira Legacy
  server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-106

   please share general SDC, MSO, AAI workarounds here
• F2F Dec 2017 presentations - Transaction Traceability using ELK by James

Minutes

• Discussed
• Discuss delimiter, new line, mdc name/value pairs
• Discuss producers (devs) as well as consumers (ops) AT&T and Bell - need to handle ops as well as NBI clients - from an indexing/parsing perspective
• Discuss use case where indexing fails and ops reads the logs directly
• Allow for default and new format toggling - could have dual appenders/or subdirs for both formats until R2? - see MSO for example in ONAP Log Locations
• maintain backward compatabilty with EELF
• Standardize in the future on logger names not different files
• Need to rework standard directory
• part of log audit - verify eelf appenders in logback.xml
  
  

...