Add 1 second granularity to ATLAS metrics

At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
reducing the granularity to 1 second would give more insight

21 votes

sudheer reddy shared this idea · Feb 24, 2020 · Report… · Admin →

completed ·

AdminFrank (Admin, MongoDB) responded · Apr 4, 2022

10-second level granularity for Atlas projects is available with M40+ clusters. More information on this is available here: https://www.mongodb.com/docs/atlas/monitor-cluster-metrics/#std-label-premium-monitoring

An error occurred while saving the comment

AdminAndrew Davidson (VP, Cloud Products, MongoDB) commented · July 16, 2021 7:08 PM · Report

We are working to introduce 10-second level granularity for Atlas projects with M40+ clusters as a next step

Submitting...
Alona commented · July 15, 2021 5:19 AM · Report

Monitoring Data Storage Granularity 5 minutes for 48 hours is not enough. It would be good to see at least 1-2 months

Submitting...
Will commented · June 10, 2021 7:28 PM · Report

Rather than increasing granularity, just reporting the `max` rather than (or in addition to) the average would go a long way towards making the metrics useful.

We have to open up a support ticket to request "FTDC diagnostic data" every time our clusters do anything weird, and it's a pain.

Submitting...
Brian commented · April 13, 2021 10:28 AM · Report

For write heavy workloads, sub-minute granularity of disk latency and IOPS would be useful to visually identify the limits of performance.

Submitting...
Michael commented · March 30, 2021 12:41 PM · Report

We have also recently had alerts for metrics that we can not see more granularly. We have configured our IOPS for what we believe our usage is but have recently found out we have occasional sub minute spikes of much higher usage.

Submitting...
Victor commented · February 16, 2021 8:11 PM · Report

Having alerts that fire from data points at a finer granularity than the metrics, it is very misleading.
In our case, multiple alerts are triggering and then you see the metrics, and all looks fine.

It makes debugging issues almost impossible.

Submitting...
Ofer commented · March 23, 2020 10:03 AM · Report

Hi Rez, please look at support case 00643354 - a short CPU usage spike causes disconnections from the server. This CPU spike is invisible to Atlas users since over a period of 1 minute the average cpu usage is smoothed down 60%.
I suggest exposing CPU (and possible network as well) at a finer granularity.

Submitting...
AdminRez (Admin, MongoDB) commented · February 25, 2020 10:29 AM · Report

Hi Sudheer - Thanks for the feedback. We are considering this. What would you reckon are the most metrics to provide <1m granularity to and why?

Submitting...