see ONAP Application Logging Specification - Post Dublin
Follows deprecated - Logging Casablanca Scope
Key words are: out of the box, reuse components, iterative changes - not major spec changes.
There is one primary use case and one enabler use case
UC1: Provide for transaction tracing via search or dashboard for distributed transactions across ONAP components - enabled by the logs shipped to the ELK stack - in real time. (the ELK stack is there - we just need to adjust log content - amount and format) UC2: Provide for UC1 tracing via standardized logs - ideally via marker/mdc (label/key:value pair) markup |
Plan is to take the portal/sdk library - align the rest of onap to this library and then add marker/mdc (labels and key/value pair) support as required in phase 2
Work will include 1) verify pipeline 2) verify logback format
Look at a standard that will allow us to use standard parsing libraries all the way to eventual AI/ML by adopting a standard like open tracing.
REST and HTTPS security
including filebeat sidecar anti-pattern/replacement, elk stack upgrade, deployment template, library language scope (python, swift...)
https://github.com/helm/helm/blob/master/docs/charts_hooks.md
Investigate out of the box prometheus monitoring
backup/restore, security, log format monitoring, elk dashboards
Lower in priority will be to align onap with requirements of Acumos and ECOMP for example - the focus will be on alignment of ONAP components only - to the primary goal of providing a transaction tracing system via the ELK stack.
Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals
In progress - was a one time casablanca static dashboard - will do an automated one with the Bell, Orange and Samsung guys
Commit or Stretch goal | Feature | Owner | Status | % complete | EPIC | Notes |
|---|---|---|---|---|---|---|
| commit | bugs | 60% | ||||
| 6.3 upgrade | 0% | Acumos and Clamp driven - need plugin/module support in 6.3 verify new filebeat version works verify indexes need upgrade strategy for future - index migration | ||||
| commit | schema | 50% | ||||
| commit | search guard | 20181113 added to scope in | ||||
| stretch | format standards for tracing | |||||
| stretch | analytics | Artificial Intelligence and Deep Learning | ||||
shipping infrastructure | starting | 20% | Verify infrastructure part 2 - add infrastructure to new pods | |||
| log level management | ||||||
| Content | 10% | Verify log content | ||||
| Library | 20180809 | Portal has a library in SDK that is already used by AAI, SDC move up | ||||
| Security | ||||||
| in progress | 30% | AOP wrapper of log4j library in LOG-115 | ||||
| Deployment | Prototype done need to retrofit | |||||
| Stretch | Not started | log testing tool | ||||
| Pluggable devops | ||||||
| Stretch | feasibility tested | 10% | expand on filebeat DaemonSet | |||
Filebeat alternatives fluentd | ||||||
| debug for devs | ||||||
| submitted | 90% | SLF4J demo library | ||||
| El-alto | CLAMP and VES alignment with Logging ELK |
Q: Tony Hansen Q about library support beyond java like Python, - heads up to MultiVim team when the spec (29 fields is approved by the arch meet next week) - to realign
Q: need a way to combine the 3 users of python and their separate libraries
Architecture revisit - should we adjust our ELK stack to use for example fluentd, or add prometheus