# Davis Anomaly Detector for "slow" metrics

**URL:** <https://community.dynatrace.com/t/davis-anomaly-detector-for-slow-metrics/53756>\
**Category:** Alerting\
**Tags:** anomaly-detection\
**Created:** [October 16, 2025, 10:10am UTC](https://community.dynatrace.com/t/davis-anomaly-detector-for-slow-metrics/53756 "2025-10-16T10:10:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![r\_weber](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/r_weber/32/24884_2.png) [@r\_weber](https://community.dynatrace.com/u/r_weber)\
**Post date:** [October 16, 2025, 10:10am UTC](https://community.dynatrace.com/t/davis-anomaly-detector-for-slow-metrics/53756/1 "2025-10-16T10:10:39Z")

</div>

The old metric events had the same limitation as seems to have the davis anomaly detector:  
I. have a “slow” metric/timeseries, where a metric data point is produced only every hour. In a normal Notebook/query I can easily apply the Anomaly Detection (Auto) with whatever window or datapoints I want, and it works fine.

However the Anomaly Detectors expect a metric resolution of 1 minute:

 ![r_weber_0-1760609261237.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/d/ddc7c7a47b2d93d52d3ddac7f2113e32fdac6e6a.png)

IMO for the anomlay detection it doesn’t matter if the datapoints are far apart or not, it is just the amount of datapoints that is relevant, right? So for a “slow” metric I’d like to analyze a longer timeframe of 72h (=72 datapoints) and not just e.g 1h with - in a one minute requirement - 60 datapoints.

---

<div class="post-metadata">

**Author:** ![JeanBlanc](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jeanblanc/32/25897_2.png) [@JeanBlanc](https://community.dynatrace.com/u/JeanBlanc)\
**Post date:** [October 24, 2025, 9:51am UTC](https://community.dynatrace.com/t/davis-anomaly-detector-for-slow-metrics/53756/2 "2025-10-24T09:51:38Z")

</div>

Hi&nbsp;[@r\_weber](https://community.dynatrace.com/user/35901)

Yes, that’s correct — this is indeed a **limitation of the Davis Anomaly Detector**.

Just like with the old metric events, the detector currently expects **a 1-minute metric resolution** and only analyzes data **within the defined window size (up to 1 hour maximum)**.

So, for “slow” metrics with hourly data points, the Davis Anomaly Detector won’t perform well, as it doesn’t adapt its analysis window to the lower data frequency.

Best regards,

Jean
