Hello Michael,

Regarding to the Marker, it is still a bit confusing for me. I have tried to 
summarized a bit based on the info from wiki and from your previous emails, 
could you please have a look and let me know whether my understanding is 
correct?

Just to mention, Clamp is using EELF as the logging framework.

Imaging the following scenario:

  1.  Component A triggers Clamp API -> Marker ENTRY in the AUDIT log of Clamp
  2.  Clamp triggers API of component B for a synchronous call -> Marker 
INVOKE-SYNCHRONOUS in AUDIT log of Clamp?
  3.  Component B returns the API call of Clamp -> Marker INVOKE-RETURN in 
component B log?
  4.  Clamp exits the API call -> Marker EXIT in the METRICS log? Marker 
INVOKE-RETURN in Clamp AUDIT log, since it returns the API call of Component A?

You have also mentioned in your previous email that, the goal is to use 1 file 
to store all the logs, but use Markers to distinguish debug/error/audit. So it 
means we don't really care whether the market is written into Audit log or 
Metrics log, right? As long as the marker is logged correctly into 1 file, that 
will be enough. Thanks for your reply in advance!

Kr,

Xue


From: OBRIEN, FRANK MICHAEL
Sent: Wednesday, August 01, 2018 5:27 PM
To: Gao, Xue <[email protected]>; [email protected]
Cc: Ngueko, Gervais-Martial <[email protected]>
Subject: RE: [onap-discuss][clamp ][LOG]ONAP Application Logging Specification 
v1.2

Xue,
   Hi, good question - you have 4 options (unchanged, do your own code 
changes/library, use the SLF4J library from Luke (includes MDC/Marker support) 
or use the AOP (WIP) wrapper on the SLF4J library - it uses aspects to (so-far) 
add ENTRY/EXIT marker (labelled) logs for each function call in scope.

Using the library is optional - the goal is to reduce the amount of work teams 
need to do to adhere to the new MDC/Marker specification for Casablanca.  The 
example RI below is a reference of how to use the library and a place for the 
logging team to exercise every MDC and test transactions without having to rely 
on real ONAP components - its own integration test suite.

    There are developer details on using the libraries (pom.xml edits, spring 
AOP additions) and how to deploy the logdemo pod alongside onap that demos 
using the libraries
https://wiki.onap.org/pages/viewpage.action?pageId=28378955#ONAPApplicationLoggingSpecificationv1.2(Casablanca)-DeveloperGuide<https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_pages_viewpage.action-3FpageId-3D28378955-23ONAPApplicationLoggingSpecificationv1.2-28Casablanca-29-2DDeveloperGuide&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=5RojxS3mGeRiSndq4IXx3SozHcM4wUD2s1ZVFmT4nos&e=>
    The code is ready for use as we finish the library (java is most up to date 
for now, python is in progress)
https://git.onap.org/logging-analytics/tree/reference<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=kyLqpUHQC8QY7fPjfLd4DAme_cCXaiQczKOTbZpQDjE&e=>
The demo RI stack
oom kubernetes chart
https://git.onap.org/logging-analytics/tree/reference/logging-kubernetes<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference_logging-2Dkubernetes&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=Z_25ltQKVB-Ld9IE3HL5Swe_d9RW7lBfpI1MMUUEYqo&e=>
docker build
https://git.onap.org/logging-analytics/tree/reference/logging-docker-root/logging-docker-demo<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference_logging-2Ddocker-2Droot_logging-2Ddocker-2Ddemo&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=lXsCp6ifOGAoeE8Y_1swoSc-Phl3kKC02rLZZBK6Uwg&e=>
war
https://git.onap.org/logging-analytics/tree/reference/logging-demo<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference_logging-2Ddemo&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=5YOhLBI47uX3g0lDI2kvBcjO7n9M8Qfzd8yEeAV1hbg&e=>
aop library jar (wraps slfj4j library jar)
https://git.onap.org/logging-analytics/tree/reference/logging-library<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference_logging-2Dlibrary&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=4beZPcRJx504XRuGuOk9QwVY0Sdaq5kAnNW8n4Fu9VI&e=>
slf4j library jar
https://git.onap.org/logging-analytics/tree/reference/logging-slf4j<https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_logging-2Danalytics_tree_reference_logging-2Dslf4j&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=BMZn0qkemOuot9yJe8PkF7YYITdGzHdECSO6HEs2wtU&e=>

thank you
/michael


From: Gao, Xue <[email protected]<mailto:[email protected]>>
Sent: Tuesday, July 31, 2018 10:35 AM
To: [email protected]<mailto:[email protected]>; Michael 
O'Brien <[email protected]<mailto:[email protected]>>
Cc: Ngueko, Gervais-Martial <[email protected]<mailto:[email protected]>>
Subject: [onap-discuss][clamp ][LOG]ONAP Application Logging Specification v1.2

Hello Obrien,

>From the wiki page of ONAP Application Logging Specification v1.2, I have seen 
>the source code for org.onap.logging-analytics:logging-analytics project.

May I ask, are we suppose to use that project as the logging framework, or it 
is just an example and each component can create their own way of logging. Also 
is there a plan to create a standard library, so that all ONAP components can 
just use it?

Kr,

Xue

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=IlDIQNNgMj8xrV4PZJk9kPbU5xq74zJ_Tv0uUDCGldU&m=0luchpI1YpXoNhxEjz0ab7d3AdVAcGxCeuXr5xyDBCo&s=XPyf_vKDP1MmOH7vC4iFtmhrPOw9zBfH6J7IexdQRzM&e=>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11646): https://lists.onap.org/g/onap-discuss/message/11646
Mute This Topic: https://lists.onap.org/mt/23903990/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to