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

Audit StreamableReplicaSetMonitor Log Statements

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Cluster Scalability
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      It turns out we have a bunch of log statements like this one here. These statements are currently logged at info and in the default domain like so:

      {"t":{"$date":"2020-06-17T17:15:09.227+00:00"},"s":"I",  "c":"-",        "id":4333223, "ctx":"LogicalSessionCacheRefresh","msg":"RSM now monitoring replica set","attr":{"replicaSet":"repl0","nReplicaSetMembers":3}}
      

      We should only be logging at Info when we notice a new topology. Otherwise, we should be logging at D2 or above. We should also using full sentences and avoiding internal acronyms in log statements.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: