Considering adding a name or label field to the ObservableMutexRegistry to differentiate different instances of mutexes with the same tag

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Networking & Observability
    • N&O 2026-03-16, N&O 2026-03-30
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the server, there may be multiple instances of a class that registers a mutex in the ObservableMutexRegistry under one tag. For example, there are multiple ConnectionPool instances that all register their mutex with the tag ConnectionPool::_mutex. This is desired so we can see aggregated stats over all ConnectionPool mutexes, however we may also want to easily determine stats for the mutex of a specific ConnectionPool instance. We should consider adding a field to the registry that could hold a more descriptive label per mutex (for example, the name of the ConnectionPool).

            Assignee:
            Unassigned
            Reporter:
            Cole Harbeck
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: