# Metrics Correlation

**URL:** <https://community.netdata.cloud/t/metrics-correlation/173>\
**Category:** General\
**Tags:** announcement\
**Created:** [July 24, 2020, 3:54pm UTC](https://community.netdata.cloud/t/metrics-correlation/173 "2020-07-24T15:54:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![zack](https://avatars.discourse-cdn.com/v4/letter/z/f6c823/32.png) [@zack](https://community.netdata.cloud/u/zack)\
**Post date:** [July 24, 2020, 3:54pm UTC](https://community.netdata.cloud/t/metrics-correlation/173/1 "2020-07-24T15:54:54Z")

</div>

It is time consuming to go over thousands of metrics and hundreds of charts to manually identify metrics which are correlated.

!

 ![1595606066602-metrics-correlation.png](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/1X/e9cf1a2aed89d0363c4ec7ad69b31039a978e669.png)  
_Correlated Metrics_

For a specific time window when an anomaly occurred it should be possible to automatically find a subset of charts where for the same time window the same anomaly was detected.  
Let’s say a software issue resulted in high CPU and disk load over thirty seconds during an outage. Selecting that time window for the CPU load chart will provide users with the option to ask Netdata to find correlated charts. Netdata can then display the disk load chart automatically, while also hiding charts that are not relevant.  
This will allow you to very quickly narrow down all the metrics being affected by a specific issue, saving a lot of time in debugging specific software or infrastructure issues.  
We also want users to be able to share specific correlations they have found by sharing a link with their team.

---

<div class="post-metadata">

**Author:** ![OdysLam](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/odyslam/32/98_2.png) [@OdysLam](https://community.netdata.cloud/u/OdysLam)\
**Post date:** [September 22, 2020, 7:18pm UTC](https://community.netdata.cloud/t/metrics-correlation/173/2 "2020-09-22T19:18:53Z")

</div>

Thanks @andrewm4894 for keeping this up to date!

---

<div class="post-metadata">

**Author:** ![andrewm4894](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/andrewm4894/32/125_2.png) [@andrewm4894](https://community.netdata.cloud/u/andrewm4894)\
**Post date:** [September 22, 2020, 5:39pm UTC](https://community.netdata.cloud/t/metrics-correlation/173/3 "2020-09-22T17:39:42Z")

</div>

done and live to play with: [Introducing our first Netdata Cloud Insights feature: Metric Correlations for faster root cause analysis - Netdata](https://www.netdata.cloud/blog/netdata-cloud-metric-correlations/)

---

<div class="post-metadata">

**Author:** ![andrewm4894](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/andrewm4894/32/125_2.png) [@andrewm4894](https://community.netdata.cloud/u/andrewm4894)\
**Post date:** [July 28, 2020, 3:49pm UTC](https://community.netdata.cloud/t/metrics-correlation/173/4 "2020-07-28T15:49:01Z")

</div>

Working on this at the moment - happy to chat in more detail about it with anyone interested, just reply in here.