[SERVER-2741] Centralize shard cluster logging Created: 11/Mar/11 Updated: 06/Dec/22 Resolved: 03/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 1 |
| Labels: | tommaso-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Participants: |
| Description |
|
The logging of balancer operations, along with associated warnings and errors, is currently distributed across the entire shard cluster. As a result, the only way to get a complete picture of what's going on with a shard cluster is to examine the log files generated by all the various mongos and mongod processes therein. This results in a lot of time spent diagnosing even simple issues. It'd be nice if we could log all major sharding operations and errors to a central collection located in the config servers. This would greatly simplify monitoring and investigating the cluster as a whole. |
| Comments |
| Comment by Tommaso Tocci [ 03/Dec/21 ] |
|
Most of the important sharding operations are logged in either `config.actionlog` or `config.changelog` collections in the config server. For all the other logging produced by the nodes in the cluster I would suggest to use an external log aggregator software. |