[SERVER-19007] Built-in facility for full-time diagnostic data capture Created: 17/Jun/15  Updated: 22/Mar/17  Resolved: 14/Sep/15

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: 3.1.8

Type: New Feature Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Mark Benvenuto
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-19583 Implement full-time diagnostic data c... Closed
depends on SERVER-19584 Implement full-time diagnostic data c... Closed
depends on SERVER-19585 Implement full-time diagnostic data ... Closed
is depended on by DOCS-6166 Document Full-time diagnostic capture... Closed
Related
related to SERVER-20397 Metric data field is not zlib compressed Closed
Backwards Compatibility: Fully Compatible
Sprint: Platform 8 08/28/15, Platform 7 08/10/15, Platform 9 (09/18/15)
Participants:

 Description   

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.


Generated at Thu Feb 08 03:49:31 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.