Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-47867

[BP MB-45874 7.0.2] - Always emit the first exception to the application log then summarize

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Cheshire-Cat
    • 7.0.2
    • eventing
    • Untriaged
    • 1
    • Unknown

    Description

      The developer experience for logging exceptions to the Application log (MB-31920) is poor.
       
      Right now when in a dev cycle working on a new script it is a bit perplexing when you wait on average 30 seconds (and up to 60 seconds) to see the exception (along with a count) be emitted.

      • We could always the very first message, i.e. count===1 immediately the first time we see the exception after any deployment or any resume.
      • Then we fall back to the current behaviour of summarization only on count === 2-N ( or minute two+ on 1-N) summarize and emit once per minute. 

       
      This would speed up initial debug feedback to the developer for quicker understanding of the issue and still limit overwhelming logging.
       

      Attachments

        Issue Links

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

          Activity

            There are no commits yet on this issue.

            People

              srinivasan.raman Srinivasan Raman
              jeelan.poola Jeelan Poola
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty