[SERVER-48984] Audit StreamableReplicaSetMonitor Log Statements Created: 18/Jun/20  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: neweng, sharding-nyc-subteam2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Participants:
Story Points: 2

 Description   

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.



 Comments   
Comment by Lauren Lewis (Inactive) [ 21/Dec/21 ]

We haven’t heard back from you in at least 1 year, so I'm going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:18:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.