Uploaded image for project: 'Logging analytics'
  1. Logging analytics
  2. LOG-115

Logging RI - SLF4J

    XMLWordPrintable

Details

    • Epic
    • Status: Closed
    • Medium
    • Resolution: Won't Do
    • None
    • Dublin Release
    • None
    • LOG Sprint 8, LOG Sprint 11

    Description

      Card

      As an ONAP developer, I want a reference example for non-EELF logging. 

      Conversation

      We want a minimal, coherent, compliant example which shows:

      1. Logging via SLF4J. 
      2. Two components, A and B, where:
        1. Tests call A via REST. 
        2. A calls B via REST. 
      3. Initialization/propagation/logging of transaction ID. 
      4. Initialization/propagation/logging of invocation ID. 
      5. Propagation of other MDCs including (but not limited to) FromAppId and PartnerName.
      6. Testcases which:
        1. Initiate a (dummy) request.
        2. Parse and verify output from components A and B.

      This will exercise canonicalized provider configuration, and will probably assist in its development and/or refinement. 

      EELF and non-EELF examples should be equivalent.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-117 Logging RI - Containerization

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. LOG-507 POMBA as RI/Demo of Casablanca Logging spec/library compliance - deployment/helm and runtime

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. LOG-596 logging unit test expects unix line endings - fails on win64 systems

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-116 Logging RI - EELF

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-126 Validate JDK 11

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Task - A task that needs to be done. LOG-128 Investigate new JEP-158/271 unified logging in JDK 9-11

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          links to

          Web Link https://gerrit.onap.org/r/#/c/46569/

          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              lparker Luke Parker
              lparker Luke Parker
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: