[SERVER-77875] Create stall monitor for all commands that Cloud Monitoring uses Created: 07/Jun/23 Updated: 07/Nov/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Security Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Server Security
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
SERVER-76723 proposes an FTDC stall monitor, we should similarly have one for Cloud Monitoring commands, similar to "serverStatus is slow" log messages (though with a better format, see SERVER-77032). Cloud Monitoring uses: hello/isMaster, serverStatus, replSetGetStatus, collstats, buildInfo, _isSelf, getCmdLineOpts, getLog, hostInfo, connPoolStats, dbStats |