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

During development, provide a mechanism to log in logv2 without providing a logid

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging
    • Labels:

      During development it's occasionally desirable to be able to cheaply sprinkle log messages into source code to aid in debugging (printf style debugging). logv2 makes this painful, by requiring logids for each message (requiring some kind of elaborate provisioning system for what previously could have been as inexpensive as copy/paste).

      If we could provide a special log macro, or allow a special logid, that was usable in local development and for patch builds (but not allowable through the commit queue) that would enable that use case, while still enforcing that log messages have ids in production builds.

            backlog-server-devtools DO NOT USE - Backlog - Dev Tools
            mira.carey@mongodb.com Mira Carey
            1 Vote for this issue
            9 Start watching this issue