# Problem with metrics built-in

**URL:** <https://community.dynatrace.com/t/problem-with-metrics-built-in/53185>\
**Category:** Cloud platforms\
**Tags:** aws, dynatrace-managed\
**Created:** [September 1, 2025, 12:52pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185 "2025-09-01T12:52:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gustavodutra](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gustavodutra/32/35020_2.png) [@gustavodutra](https://community.dynatrace.com/u/gustavodutra)\
**Post date:** [September 1, 2025, 12:52pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/1 "2025-09-01T12:52:06Z")

</div>

Hi, everyone,

Has anyone here experienced issues with AWS Lambda built-in metrics?

Recently, I noticed that the Lambdas configured in my AWS environment have been failing frequently, and Dynatrace received the error metrics but did not generate any alerts.

Dynatrace has the capability to connect with the AWS environment and bring insights into the tool. It works reasonably well, but it’s usable.

Has anyone else been through this?

 ![gustavodutra_0-1756731118626.png](https://global.discourse-cdn.com/dynatrace/original/1X/a3740a1c09e0ceb2229f96381368863f61bf5e8d.png)

---

<div class="post-metadata">

**Author:** ![dawid\_kaszubski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dawid_kaszubski/32/34412_2.png) [@dawid\_kaszubski](https://community.dynatrace.com/u/dawid_kaszubski)\
**Post date:** [September 1, 2025, 1:11pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/2 "2025-09-01T13:11:41Z")

</div>

Hi&nbsp;[@gustavodutra](https://community.dynatrace.com/user/56702),

Dynatrace, by default, triggers an alert when the failed invocations rate is higher than 5%.

You can check the alert configuration in “Anomaly detection for classic AWS services” tab in Settings classic.

---

<div class="post-metadata">

**Author:** ![gustavodutra](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gustavodutra/32/35020_2.png) [@gustavodutra](https://community.dynatrace.com/u/gustavodutra)\
**Post date:** [September 1, 2025, 1:23pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/3 "2025-09-01T13:23:15Z")

</div>

Hi,&nbsp;[@dawid\_kaszubski](https://community.dynatrace.com/user/25915).

How are you?

I don’t find this option, could you send me an example screenshot or the referenced URL?

 ![gustavodutra_0-1756732985812.png](https://global.discourse-cdn.com/dynatrace/original/3X/4/2/4237b6996224dfc6e59f14e15699ce88243e026b.png)

---

<div class="post-metadata">

**Author:** ![gustavodutra](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gustavodutra/32/35020_2.png) [@gustavodutra](https://community.dynatrace.com/u/gustavodutra)\
**Post date:** [September 1, 2025, 2:10pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/4 "2025-09-01T14:10:01Z")

</div>

I found the option below in automatic mode and changed it to custom settings, setting a threshold of 5%; however, the lambdas aren’t triggering alarms.

I have two lambdas that have 100% failure rates and aren’t generating any alerts.

 ![gustavodutra_0-1756735782120.png](https://global.discourse-cdn.com/dynatrace/original/3X/f/b/fb834f1246bc47ac16f18a25a356a450a113075d.png)

---

<div class="post-metadata">

**Author:** ![dawid\_kaszubski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dawid_kaszubski/32/34412_2.png) [@dawid\_kaszubski](https://community.dynatrace.com/u/dawid_kaszubski)\
**Post date:** [September 1, 2025, 2:12pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/5 "2025-09-01T14:12:29Z")

</div>

You can find the “Anomaly detection for classic AWS services”&nbsp;page, by clicking “AWS” in the “Anomaly detection” section.&nbsp;  
URL:

```java
<the tenant url>/ui/apps/dynatrace.classic.settings/ui/settings/builtin:anomaly-detection.infrastructure-aws

```

---

<div class="post-metadata">

**Author:** ![gustavodutra](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/gustavodutra/32/35020_2.png) [@gustavodutra](https://community.dynatrace.com/u/gustavodutra)\
**Post date:** [September 16, 2025, 2:21pm UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/6 "2025-09-16T14:21:56Z")

</div>

Guys, I managed to get around this by increasing the sliding window and dealership sample.

I set both to 60, and the alerts appeared, and they seem to be helping.

 ![gustavodutra_0-1758032509491.png](https://global.discourse-cdn.com/dynatrace/original/2X/3/32d50315cc24283a10a9d6c1be1529d8933a0622.png)

---

<div class="post-metadata">

**Author:** ![izabelarokita](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/izabelarokita/32/41812_2.png) [@izabelarokita](https://community.dynatrace.com/u/izabelarokita)\
**Post date:** [December 17, 2025, 9:38am UTC](https://community.dynatrace.com/t/problem-with-metrics-built-in/53185/7 "2025-12-17T09:38:43Z")

</div>

Happy to hear you have found a solution,&nbsp;@gustavodutra,&nbsp;and thanks for sharing it with our Community!&nbsp;:blush:
