Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-46382

Alter LOGV2 behavior in the presence of missing attributes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.4
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • Fully Compatible
    • ALL
    • Dev Tools 2020-02-24, Dev Tools 2020-03-09

      It's my understanding that LOGV2 expressions throw when presented with attribute substitutions in the message that are not present in the overall expression. I'd like them to be fatal in debug builds and non-throwing elsewhere (perhaps logging some extra context that an attribute is missing).

      Failure to do this will turn typos in log statements in exception unsafe areas of code into fatal errors in production, which feels excessive.

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            mira.carey@mongodb.com Mira Carey
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: