Logging Dublin M3 Architecture Review

1. Brief Project Overview (brief as it should be known)
   1. Logging deploys an ELK stack set of containers via OOM (Logstash, ElasticSearch and Kibana) - selected onap components add a filebeat sidecar container to ship/stream formatted logs to this elk stack - see the diagram with the small boxes streaming logs to this ELK stack.
      
      
      
      
2. New component capabilities for Dublin, i.e. the functional enhancements.
   1. get as many projects as possible to adopt the casablanca logging guidelines
   2. work on the dublin logging guidelines changes for adoption in elalto - minimal so far
   3. prometheus work was slated but has been moved to the OOM scope
3. New or modified interfaces
   1. none
4. If they are modified, are the backwards compatible?
5. Interface naming (point to an example)

6. Reference to the interfaces.

   
   
7. What are the system limits?

H/A using Kubernetes, will need pod anti-affinity rules for some components like AAI (AAI and logstash not on the same K8S cluster VM).

1. Involved use cases, architectural capabilities or functional requirements.
   1. Any that cause transaction logs in any ONAP component currently streaming logs
   2. not to be confused with the CLAMP elk stack
2. Listing of new or impacted models used by the project (for information only).
   
   1. None