Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-3531

Log level improvement for SO component

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Not a Bug
    • Icon: Low Low
    • None
    • None

      I am a engineer at the French company Sopra Steria where we work on ONAP for our client Orange (Sylvain Desbureaux and Eric Debeau).

      In our work, we have noticed that some caught exceptions are not logged or are logged as "debug".

      This makes it a bit problematic for us, as some errors might not be shown in production (debug mode is too verbose).

      We did a review of all logging methods that are inside catch blocks and we believe some of them can get their level changed.  In total, 52 logging method that are currently as "debug" can be changed to better fit the severity of the exception.

      It would be a pleasure to chat with you to discuss this more in-depth and figure out if our suggestions can be a useful contribution to the project.

      Kindly, Othman

            seshukm seshukm
            ontahm ontahm
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: