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

Fix malformed LOGV2 and assertion IDs

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc13, 4.7.0
    • Affects Version/s: None
    • Component/s: Logging
    • None
    • Minor Change
    • v4.4
    • Service arch 2020-07-13
    • 22

      According to the LOGV2 documentation, programmers should use the following to choose log IDs:

      The ID is a signed 32bit integer in the same number space as the error code numbers. It is used to uniquely identify a log statement. If changing existing code, using a new ID is strongly advised to avoid any parsing ambiguity. When selecting ID during work on JIRA ticket SERVER-ABCDE you can use the JIRA ticket number to avoid ID collisions with other engineers by taking ID from the range ABCDE00 - ABCDE99.

      However, there are multiple instances in the code-base such as this one, where we have not followed the above pattern to pick log and assertion identifiers. This ticket should find all instances of malformed LOGV2 and assertion identifiers and replace them with new IDs, generated by employing the above pattern.

            Assignee:
            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            Reporter:
            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: