-
Type: New Feature
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Diagnostics
-
None
-
Fully Compatible
-
Platform 8 08/28/15, Platform 7 08/10/15, Platform 9 (09/18/15)
Diagnosing one-time incidents and ongoing problems in the field often requires asking the customer to reproduce a problem while collecting wide-coverage, high-resolution, long-retention data, for example serverStatus timeseries at 1-second intervals. However this is problematic for a few reasons
- reproducing the problem may be impossible, difficult, or inconvenient for the customer
- the mechanics of collecting diagnostic data with external tools such as mongo shell scripts are often problematic, particularly if the data needs to be collected over an extended period (days or weeks) - servers get restarted, data collection is accidentally terminated, instructions are not followed carefully, it is additional inconvenience for a customer who may have already been severely inconvenienced by a problem in MongoDB, and so on.
Serviceability would improved by a built-in facility to capture such data, compress it, and store it, while using minimal resources such that the facility can be left on full-time in production.
- depends on
-
SERVER-19583 Implement full-time diagnostic data capture compressor and decompressor
- Closed
-
SERVER-19584 Implement full-time diagnostic data capture file reader and writer
- Closed
-
SERVER-19585 Implement full-time diagnostic data capture MongoD integration
- Closed
- related to
-
SERVER-20397 Metric data field is not zlib compressed
- Closed