# Davis Anomaly Detector not able to select extension metrics

**URL:** <https://community.dynatrace.com/t/davis-anomaly-detector-not-able-to-select-extension-metrics/48059>\
**Category:** Alerting\
**Tags:** anomaly-detection\
**Created:** [September 30, 2024, 7:07pm UTC](https://community.dynatrace.com/t/davis-anomaly-detector-not-able-to-select-extension-metrics/48059 "2024-09-30T19:07:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [September 30, 2024, 7:07pm UTC](https://community.dynatrace.com/t/davis-anomaly-detector-not-able-to-select-extension-metrics/48059/1 "2024-09-30T19:07:44Z")

</div>

If possible, can someone please confirm that I haven’t lost my mind just yet?

Dynatrace Davis Anomaly Detector can convert and create new metric alerts. However, when I target a metric that begins with ext: it cannot find the data.

 ![ChadTurner_0-1727723117177.png](https://global.discourse-cdn.com/dynatrace/original/3X/a/5/a5f207d6268380d914446cc4a5cf138ecca06718.png)

But if I use a metric that is no ext:, it works no problem:

 ![ChadTurner_1-1727723170552.png](https://global.discourse-cdn.com/dynatrace/original/3X/0/f/0f8babf73f3aed92e6e3c2744a569a174a5ba0b3.png)

If it is a limitation then I can put in a RFE, I just want to make sure its not me and that it is the functionality of the platform.

---

<div class="post-metadata">

**Author:** ![Gosia\_Murawska](https://avatars.discourse-cdn.com/v4/letter/g/2bfe46/32.png) [@Gosia\_Murawska](https://community.dynatrace.com/u/Gosia_Murawska)\
**Post date:** [December 2, 2024, 12:34pm UTC](https://community.dynatrace.com/t/davis-anomaly-detector-not-able-to-select-extension-metrics/48059/2 "2024-12-02T12:34:14Z")

</div>

Hi&nbsp;[@ChadTurner](https://community.dynatrace.com/user/14877), have you managed to solve this problem?

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [December 2, 2024, 2:23pm UTC](https://community.dynatrace.com/t/davis-anomaly-detector-not-able-to-select-extension-metrics/48059/3 "2024-12-02T14:23:50Z")

</div>

Hello&nbsp;[@GosiaMurawska](https://community.dynatrace.com/user/77704),&nbsp;I actually just recently found a loop hole 🙂 If you make the metric in the Data Explorer, convert it to advanced mode and build a classic Event Metric using that Metric Selector String, you can now port that over to the Davis Anomaly Detector.

I hope this helps 🙂
