Thank you Jason and Michael, appreciate the feedback. Thanks, Randa
From: OBRIEN, FRANK MICHAEL Sent: Monday, January 15, 2018 2:34 PM To: Jason Hunt <djh...@us.ibm.com>; MAHER, RANDA <rx1...@att.com>; Luke Parker <lpar...@amdocs.com> Cc: onap-discuss@lists.onap.org; onap-rele...@lists.onap.org Subject: RE: [s3p][logging] Level 1 met with EELF? Randa, Hi, yes as long as you are following the current logging guidelines for Beijing you should be good. Try to use EELF 1.0.0 not 0.0.1 - appc is currently pushing logs to the ELK stack - not tested as much yet as we rarely get to closed-loop for the vFW. There is a difference wiki on the changes between Amsterdam and Beijing for the guidelines - minimal changes. https://wiki.onap.org/display/DW/What%27s+New+-+ONAP+Application+Logging+Guidelines<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_What-2527s-2BNew-2B-2D-2BONAP-2BApplication-2BLogging-2BGuidelines&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=8pvzoK3bcCwVUVb5Dd61p93s7yrRfWOkusKmqpveVGQ&e=> Also an RI for all projects is being developed that component teams can reference shortly that will be a logging config, usage and deployment example. https://jira.onap.org/browse/LOG-118<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_LOG-2D118&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=xlVK9P_WbUTZDOBolgNfYvenMnn4JhDaKzcY_r1JW6E&e=> The current state of logging capture via OOM filebeat container/microservice into the OOM ELK stack pod is described below https://wiki.onap.org/display/DW/Logging+Reference+Implementation#LoggingReferenceImplementation-DI2:20171231:Audit:EELFimplementors<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_Logging-2BReference-2BImplementation-23LoggingReferenceImplementation-2DDI2-3A20171231-3AAudit-3AEELFimplementors&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=ptTWMPEvrg3d98fOFTdT3vaBiuVKB1anpJCENyU8QBA&e=> For example the aai, appc, mso, policy, portal, sdc, sdnc and vid projects currently stream logs into the ELK stack - so are essentially compliant beyond a completed format/location audit. Where the appc project has 1 of its' 3 containers (the ODL app) retrofitted with a sidecar container pattern<https://urldefense.proofpoint.com/v2/url?u=https-3A__kubernetes.io_docs_concepts_cluster-2Dadministration_logging_-23streaming-2Dsidecar-2Dcontainer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=uXtKVRKFjEVhyyAAcUr1sMVdfgGiw3SagrheTUJMwfA&e=> in the form of a filebeat sister container in their yaml - for reference sdnc has its ODL app and DB containers configured - but it is the only component that logs from its DB. Appc along with dmaap, part of policy, deprecated projects of aai and so run the older 0.0.1 version of ELK not the current 1.0.0 version. I am currently verifying what is different between 0.0.1 and 1.0.0 - likely I will just raise a jira to push up the version in your pom and retest. https://github.com/att/EELF<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_att_EELF&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=aU_0DAQiuh6_V3JwC0j-Q4915Fba_2O5hEpyx-AiGnw&e=> Thank you /michael From: Jason Hunt [mailto:djh...@us.ibm.com] Sent: Monday, January 15, 2018 12:19 To: MAHER, RANDA <rx1...@att.com<mailto:rx1...@att.com>> Cc: LEFEVRE, CATHERINE <cl6...@intl.att.com<mailto:cl6...@intl.att.com>>; MCCRAY, CHRISTOPHER <cm6...@att.com<mailto:cm6...@att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>; Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Subject: Re: [s3p][logging] Level 1 met with EELF? Randa, Thanks for the question. The "single logging system" would be under the scope of the Logging Enhancement project. If you are following all of their guidelines (which includes EELF) so that they can pull in your logs, you should be good. Look to that team (Michael O'Brien) for further guidance. Regards, Jason Hunt Executive Software Architect, IBM Phone: 314-749-7422 Email: djh...@us.ibm.com<mailto:djh...@us.ibm.com> Twitter: @DJHunt From: "MAHER, RANDA" <rx1...@att.com<mailto:rx1...@att.com>> To: Jason Hunt <djh...@us.ibm.com<mailto:djh...@us.ibm.com>> Cc: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>" <onap-rele...@lists.onap.org<mailto:onap-rele...@lists.onap.org>>, "LEFEVRE, CATHERINE" <cl6...@intl.att.com<mailto:cl6...@intl.att.com>>, "MCCRAY, CHRISTOPHER" <cm6...@att.com<mailto:cm6...@att.com>> Date: 01/15/2018 10:06 AM Subject: [s3p][logging] Level 1 met with EELF? ________________________________ Hello Jason, I was looking for some clarification on the Manageability requirement for Level 1. APPC and many other components of the ONAP support EELF for standardized logging. If a project supports EELF, can we assume it is at Level 1 or where you looking for something different under this area? Manageability * Level 1: * All ONAP components will use a single logging system. Thanks, Randa This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=kyPZ229JImvwwKH-78nlyg&m=fCDWnb739a6SBqT73xwpTtWZH7niknZhBp_UdcMa7ec&s=8mX8aiNhDF8WQ0HTL_cTVgb3HJtb6bQAy_gH6yvqju8&e=>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
