Details

    Description

      Eventing log files are not helpful enough at INFO and unusably verbose at debug and trace. The team must visit each log line and:

      1. Log only useful information at INFO level
      2. Log more info at DEBUG level but not so much that it can't be turned on in production
      3. Log step-by-step of what the product is doing at TRACE level

      Notes:
      In #1 – there are recurring messages that convey no useful info. These need to be suppressed until the content changes
      In #2 – we need to reduce verbosity. developers should be able to turn on debug during development and admins in production if trouble arises
      In #3 – some parts of code don't have enough logs. we need to add more trace logging

      Attachments

        Issue Links

          For Gerrit Dashboard: MB-35549
          # Subject Branch Project Status CR V

          Activity

            People

              ankit.prabhu Ankit Prabhu
              siri Sriram Melkote (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are 2 open Gerrit changes

                  PagerDuty