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

Allow statuses/assertions to have both a named error code and a unique number

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

      Currently statuses/assertions can have either a named error code or a unique number. Named error codes are useful for cases which are semantically the same from the user's point of view. However for diagnosability/debuggability, unique numbers can be very helpful because you can immediately tell exactly where an error came from. So it might be nice to be able to include a unique number together with a named code, for instance in a uassert.

            Assignee:
            backlog-server-servicearch Backlog - Service Architecture
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: