Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

High Level

Features

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

Logging Alignment before enhancement

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

Open Standards

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.

Security

REST and HTTPS security 

LOG-494 - Getting issue details... STATUS

Infrastructure Improvements

including filebeat sidecar anti-pattern/replacement, elk stack upgrade, deployment template, library language scope (python, swift...)

Monitoring

Investigate out of the box prometheus monitoring

S3P

backup/restore, security, log format monitoring, elk dashboards

3rd party consumption alignment

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.

Dublin Alignment

Release 4 (Dublin) Service Providers (EUAG) Requirements / Proposals

SP priorities for Dublin

Deployment Model

In progress 

Epics

LOG-707 - Getting issue details... STATUS

Commit

or

Stretch goal

FeatureOwnerStatus% completeEPICNotes
commitbugs

60%

SO-1110 - Getting issue details... STATUS



6.3 upgrade

0%

LOG-653 - Getting issue details... STATUS

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

commitschema

50%

LOG-630 - Getting issue details... STATUS


commitsearch guard


LOG-494 - Getting issue details... STATUS

20181113 added to scope in

LOG Meeting Minutes 2018-11-13

stretchformat standards for tracing


LOG-104 - Getting issue details... STATUS



stretchanalytics


LOG-500 - Getting issue details... STATUS

Artificial Intelligence and Deep Learning

shipping

infrastructure

starting

20%

LOG-487 - Getting issue details... STATUS

LOG-852 - Getting issue details... STATUS

SO-1110 - Getting issue details... STATUS

Verify infrastructure

part 2 - add infrastructure to new pods


log level management


LOG-800 - Getting issue details... STATUS



Content
10%

LOG-178 - Getting issue details... STATUS

Verify log content

Library20180809

LOG-600 - Getting issue details... STATUS

Portal has a library in SDK that is already used by AAI, SDC

move up


Security

LOG-409 - Getting issue details... STATUS




in progress30%

LOG-95 - Getting issue details... STATUS

LOG-118 - Getting issue details... STATUS

AOP wrapper of log4j library in LOG-115

Deployment

Prototype done

need to retrofit


LOG-560 - Getting issue details... STATUS


Stretch
Not started

LOG-480 - Getting issue details... STATUS

log testing tool





LOG-190 - Getting issue details... STATUS

Pluggable devops
Stretch
feasibility tested10%

LOG-380 - Getting issue details... STATUS

expand on filebeat DaemonSet




LOG-169 - Getting issue details... STATUS

LOG-180 - Getting issue details... STATUS

Filebeat alternatives

fluentd





LOG-407 - Getting issue details... STATUS

debug for devs























submitted90%

LOG-115 - Getting issue details... STATUS

SLF4J demo library








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 


Notes

Architecture revisit - should we adjust our ELK stack to use for example fluentd, or add prometheus 

LOG-773 - Getting issue details... STATUS



  • No labels