Brief Project Overview (brief as it should be known)
- 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.
- New component capabilities for Dublin, i.e. the functional enhancements.
- get as many projects as possible to adopt the casablanca logging guidelines - ONAP Application Logging Specification v1.2 (Casablanca)
- work on the dublin logging guidelines changes for adoption in elalto - minimal so far - ONAP Application Logging Specification - Post Dublin
- prometheus work was slated but has been moved to the OOM scope - LOG-911 - Getting issue details... STATUS via OOM-1502 - Getting issue details... STATUS
- see Logging Dublin Scope
- New or modified interfaces
- none
- If they are modified, are the backwards compatible?
- Interface naming (point to an example)
- there are at least 4 logging libraries in portal/sdk, so, aai - for now projects just use their own AOP or non-AOP jar - there is an example reference since early casablanca in Logging Developer Guide#JAVA:AddingLoggingtoaWARProject - but the plan for Dublin was (more likely Elalto) - to adjust the portal/sdk library to use the proposed spec - then we get a couple projects for free as we work on the remainders - LOG-600 - Getting issue details... STATUS
Reference to the interfaces.
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).
- Involved use cases, architectural capabilities or functional requirements.
- Any that cause transaction logs in any ONAP component currently streaming logs
- not to be confused with the CLAMP elk stack
- Listing of new or impacted models used by the project (for information only).
- None