[SERVER-7662] Improve error and warning reporting in logs Created: 14/Nov/12 Updated: 14/Nov/12 Resolved: 14/Nov/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin, Logging |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Simon Harvey | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
RHEL |
||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Currently the only advice offered to monitor for errors and warnings in the MongoDB logs (for mongod, mongos and config server) is to search for the strings "error" and "warning". This tends to return too much information even when just using default verbosity for the logging and gives no indication of their criticality. Additionally much of the information returned is just noise rather than real warnings or errors (e.g. getlasterror messages). There should be a standard format for errors and warnings which includes an indication of their criticality, e.g.: ERROR-CRITICAL: This would greatly help with automated monitoring of the logs and enable a focus on the most critical issues and so a quicker response to fix issues. |
| Comments |
| Comment by Gianfranco Palumbo [ 14/Nov/12 ] |
|
Simon, This request has been already filled as
After enabling profiling, the output of the database profiler in the system.profile collection, inside the database where this profile has been enabled. Here is the documentation for Profiling – Regards, |