Parichay, Hi, answers in-line in italic-red
1. required field StatusCode<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D28378955-23ONAPApplicationLoggingSpecificationv1.2-28Casablanca-29-2DMDC-2DStatusCode&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=CQbnYWk6xBX3jNVsHm5BrQ&m=QBc6FasLTHQbno2wp4k3xffZ9wQzgLLVFIk2MBX1e5k&s=yi2-Mp4Lzxs9TqOHHcVpazGm0tQH1KiOOZYM-f8pEPY&e=> is limited to values COMPLETE, ERROR. But the vast majority of the logging invocations will be made DURING processing of a request, when it's neither complete nor failed. What should be shown? Michael: good question - limiting the enumeration was too restrictive - in the call yesterday we added INPROGRESS based on feedback from Acumos and from Dave on the spec page and Chris on the acumos page In general we will try to sync the two spec pages onap/acumos - where the onap page drives the common parts of the acumos spec https://wiki.acumos.org/display/OAM/Log+Standards https://wiki.onap.org/pages/?pageId=28378955 The larger logging/acumos logging team has been working with Portal - as of today I will be looking to use their aspect advice class in portal/sdk as a concrete RI in addition to our WIP aspect wrapper https://git.onap.org/logging-analytics/tree/reference https://git.onap.org/portal/sdk/tree/ecomp-sdk/epsdk-core/src/main/java/org/onap/portalsdk/core/logging 1. what to do about TargetElement, in Acumos we don't have virtual network functions. Michael: for targetElement - yes this is ONAP specific - this has come up a couple times - I will add a column in the spec table for non-general/industry logging MDC's (beyond the standard request/invocation ones for example) - the same type off issue that occurs in spec/proprietary jpa/orm or cloud native/agnostic artifacts in onap. I expect we will have 2 categories (industry, native(ONAP/Acumos) 1. Can we get one example of log file output columns, with all the MDC's value populated as it is generated in logs? Ex: value under RequestID, InvocationID, InstanceUUID, ServiceName, etc.. Michael: We published some examples in the spec page table - there are clickable MDC links on each line - some are missing - I will fix them. https://wiki.onap.org/pages/viewpage.action?pageId=28378955#ONAPApplicationLoggingSpecificationv1.2(Casablanca)-MappedDiagnosticContextTable Some of the older examples before we updated the spec need to be adjusted - however the developer section has output of the logging library which is being coded to implement/demo the spec https://wiki.onap.org/display/DW/Logging+Developer+Guide see example here https://wiki.onap.org/display/DW/Logging+Developer+Guide#LoggingDeveloperGuide-UseCase:SingleRESTcall-withENTRY/EXITMarkersaroundin-methodlog 1. If we don't get RequestID from header of REST calls then do we need to generate one? If so then what is the rule of generating random number? Michael: Yes, the rule is pass-through or generate - there is an example in the SLF4J library in https://git.onap.org/logging-analytics/tree/reference/logging-slf4j/src/main/java/org/onap/logging/ref/slf4j/ONAPLogAdapter.java#n103 private static UUID sInstanceUUID = UUID.randomUUID(); Thank you /michael From: DEY, SPONDON <sd4...@att.com> Sent: Monday, August 6, 2018 1:26 PM To: GUPTA, PARICHAY <pg0057...@techmahindra.com>; THAKORE, SHISHIR B <st2...@att.com>; Michael O'Brien <frank.obr...@amdocs.com>; AGRAHARAM, SANJAY <sa2...@att.com> Subject: RE: Logging Standards Adding Michael and Sanjay as well. Michael, Sanjay, See question below Thanks!! Spondon From: GUPTA, PARICHAY Sent: Monday, August 06, 2018 1:25 PM To: DEY, SPONDON <sd4...@att.com<mailto:sd4...@att.com>>; THAKORE, SHISHIR B <st2...@att.com<mailto:st2...@att.com>> Subject: Logging Standards HI Shishir/Spondon, Please address below queries team have related to logging standards. 1. required field StatusCode<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D28378955-23ONAPApplicationLoggingSpecificationv1.2-28Casablanca-29-2DMDC-2DStatusCode&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=CQbnYWk6xBX3jNVsHm5BrQ&m=QBc6FasLTHQbno2wp4k3xffZ9wQzgLLVFIk2MBX1e5k&s=yi2-Mp4Lzxs9TqOHHcVpazGm0tQH1KiOOZYM-f8pEPY&e=> is limited to values COMPLETE, ERROR. But the vast majority of the logging invocations will be made DURING processing of a request, when it's neither complete nor failed. What should be shown? 2. what to do about TargetElement, in Acumos we don't have virtual network functions. 3. Can we get one example of log file output columns, with all the MDC's value populated as it is generated in logs? Ex: value under RequestID, InvocationID, InstanceUUID, ServiceName, etc.. 4. If we don't get RequestID from header of REST calls then do we need to generate one? If so then what is the rule of generating random number? Appreciate your help!! Thanks, Parichay ============================================================================================================================ Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=CQbnYWk6xBX3jNVsHm5BrQ&m=QBc6FasLTHQbno2wp4k3xffZ9wQzgLLVFIk2MBX1e5k&s=IGNvCdlkZNKBor2E70PYw5I4sWKGPnGjlUy2CBnZXf4&e=> externally http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=CQbnYWk6xBX3jNVsHm5BrQ&m=QBc6FasLTHQbno2wp4k3xffZ9wQzgLLVFIk2MBX1e5k&s=CL6Zhs4Q7TNy4JrKezdNR9RwCPTLfbnnYby3c-pt9d0&e=> internally within TechMahindra. ============================================================================================================================ 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://www.amdocs.com/about/email-disclaimer> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11761): https://lists.onap.org/g/onap-discuss/message/11761 Mute This Topic: https://lists.onap.org/mt/24231150/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-