LOG Meeting Minutes 2018-09-20 - M4 Code Freeze
Notes
was off Fri and part of Mon doctor/dentist
SPEC lockdown with Lorraine A. Welch last Thu
Aligned 29 ONAP and Acumos - currently 29 field logback.xml patchset 14 of https://gerrit.onap.org/r/#/c/62405/
defined in v30 of https://wiki.acumos.org/display/OAM/Log+Standards
and v111 of ONAP Application Logging Specification v1.2 (Casablanca)
M4 code freeze on Thu 20th
Full deployment fix being merged for https://lists.onap.org/g/onap-discuss/topic/oom_full_deployment_do_a/25736532?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,25736532
workaround is to --set contrib.enabled=false
1050: fixed https://gerrit.onap.org/r/#/c/67323/
CLAMP needs to add the "prune" filter to the common chart for logstash - need to coordinate - they are on 6.1.2
also coordinate with aai and pomba https://gerrit.onap.org/r/#/c/58747
Code to merge
https://gerrit.onap.org/r/#/c/62405/ - align with wiki from Thu
WIKIs to finish
merge into above Logging User Guide
JIRAs to finishhttps://lf-onap.atlassian.net/browse/LOG-630
Questions to answer
DCAE involvement
Helm deletion example - assist with 2.9.1 workaround
verify logging repo does not have maven 3.3/3.5 issue Prudence Au found in pomba repos - resolved - thanks Prudence Au
Pending Work
merge logback.xml
import portal/sdk library to log war - then add new logback.xml and adjust library to fit
retrofit slf4j and slf4j-demo to use new logback.xml - specifically each of the 29 log fields
finish logstash files plugin to remove all filebeat sidecar containers
move exiting spec + field 29 ( )to dublin spec - ONAP Application Logging Specification - Post Dublin
Expand (as Acumos has) collection from k8s system and tomcat logs (access logs for example)
quick script to validate logs fields
...
Put a JIRA in for this - Q: from
Dave Williamson - in the context of is the field "serverFQDN" useful
https://lf-onap.atlassian.net/browse/LOG-666
TODO: serverFQDN currently posts "localhost" when in a container - we are not getting the container name or the vm name without some code changes - but they are available to the kubernetes system and should be written out by filebeat/logstash
2018-08-28T16:26:57.887Z||2018-08-28T16:26:57.883Z|||7741c447-cd4f-4f0a-9e7a-9abc3eebe8c1||http-nio-8080-exec-30|/logging-demo/rest/health/health|||||INFO||||localhost|0:0:0:0:0:0:0:1|||||||org.onap.demo.logging.ApplicationService|ResponseCode=, InstanceUUID=7741c447-cd4f-4f0a-9e7a-9abc3eebe8c1, RequestID=c897a12f-fa51-4450-8645-3ee907946695, ServiceName=/logging-demo/rest/health/health, ResponseDescription=, InvocationID=067ba289-9017-462a-8d68-aa2670a04205, Severity=, InvokeTimestamp=2018-08-28T16:26:57.883Z, PartnerName=, ClientIPAddress=0:0:0:0:0:0:0:1, ServerFQDN=localhost, StatusCode=||EXIT in above ServerFQDN=localhost ClientIPAddress=0:0:0:0:0:0:0:1 VirtualServerName=(EMPTY)test a failover - especially if logstash "files" is capturing
harvester should know vm name like "a-onap-devops" - so the java library may not need to actually capture the serverFQDN
onap-msb-consul-df5cdcdbb-n8f5g 1/1 Running 0 29m 10.42.171.138 a-onap-devops
verify that the first part of the id changes on a a cluster vm redeploy "df5cdcdbb-n8f5g" - specifically the df5cdcdbb part - as the n8f5g part is the part of the id that "does" vary across pod restarts on a single VM.
all this assumes you are in ELK + logstash "files" plugin or keep "beats" + filebeat - in both cases verify server name is derived from harvester
Log checker for https://lf-onap.atlassian.net/browse/LOG-480 -
Cheuk Yiu Horace Ip will follow up
TODO:
Michael O'Brien Post good/bad logs from current spec
https://gerrit.onap.org/r/#/c/62405/13/reference/logging-demo/src/main/resources/logback.xml
TODO: verify which library they use - SO