[DRIVERS-911] Measure the impact of planned maintenance procedure on Drivers Created: 02/Mar/20  Updated: 07/Sep/22

Status: Backlog
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Esha Bhargava Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related

 Description   
Epic Summary

Summary

As part of the Atlas Planned maintenance initiative (INIT-4), the drivers will need to become more intelligent so that we as a platform can notice key indicators of issues in new releases. We also want to take note of changes to essential metrics that occur during maintenance. To accomplish that, we'd need to:

  • identify what metrics and parameters we may want to collect as the driver (DRIVERS-921)
  • protocol to report metrics to the mongod
  • report those metrics in `serverstatus`

Drivers to focus on: Node, Python and Java

Desirable metrics

Should be relevant client metrics that we do not already have available either from server or on Atlas side

Lead : TBD
Author : Rachelle Palmer
POCs : ???

Spec Update


Generated at Thu Feb 08 08:22:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.