Configuration Rollout:

• Dual appenders for the duration of R2
  • EELF - /var/log/ONAP_EELF/{component}/{subcomponent}/**
  • Indexable - /var/log/ONAP/{component}/{subcomponent}/**
• Template-based canonicalization. (See OOM).
• Revisit retention, etc.
• Retire Log4j1.2.
• Technical debt. 

Guidelines II:

• MDC semantics (existing MDCs)
• Usage, best practice
• Code examples
• Synthetic reference component:
  • REST service WAR
  • Minimal; just logging.

Invocation IDs and Call Graphs:

• Add InvocationID MDC
• Add Marker support
• Retrofit EELF to emit Markers.
• Reporting association (one or both of):
  • Message convention
  • Dedicated MDC

OOM:

• Logfile persistence:
  • Necessity. 
  • Performance of certain volume types.
• Discrete Filebeat deployment.
• Provider configuration: 
  • Externalized as ConfigMaps
  • Parameteried by Helm.
• Technical debt. expand?

QA:

• Context propagation II. (Bugs raised → ONAP projects).
• Applying conventions II. (Bugs raised → ONAP projects).
• Upgrade interaction between two key ONAP components:
  • Reference configuration. 
  • Value vs. effort. (That is, the most valuable also represent the largest effort, e.g. SO → controllers). 
• Technical debt. expand?

APIs:

• Annotations for automatic logging.
• APIs and abstractions (higher order).
• EELF enhancements (lower order)

CI:

• Jenkins targets. https://jenkins.onap.org/view/logging-analytics/ and 
• Deployments and automated tests. - see Auto Continuous Deployment via Jenkins and Kibana
• (Must be visible to ONAP. Dodged this in R1, but cannot in R2).

Other:

• Carrier grade.
• DMaaP appenders.
• Heat.
• ...