# Debug Failed Problem Notifications

**URL:** <https://community.dynatrace.com/t/debug-failed-problem-notifications/49952>\
**Category:** Troubleshooting\
**Tags:** problem-notification\
**Created:** [January 29, 2025, 11:31am UTC](https://community.dynatrace.com/t/debug-failed-problem-notifications/49952 "2025-01-29T11:31:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nikitachauhan](https://avatars.discourse-cdn.com/v4/letter/n/f08c70/32.png) [@nikitachauhan](https://community.dynatrace.com/u/nikitachauhan)\
**Post date:** [January 29, 2025, 11:31am UTC](https://community.dynatrace.com/t/debug-failed-problem-notifications/49952/1 "2025-01-29T11:31:20Z")

</div>

## Abstract

Dynatrace allows you to automatically push problem notifications to your preferred third-party incident management or ChatOps service. Open problems are continuously updated based on evolving impact and correlating events. To avoid spam notifications, problem notifications are only pushed to third-party systems when problems are initially detected and when they are ultimately resolved.

## Problem

There are times when notifications don’t reach your incident management tool.

## Troubleshooting steps

In such cases, please follow these troubleshooting steps:

**1. Check if the problem was created**

Go to the Problems page and use the available filter to look for the problem.

For example, my problem is “Test123”.

 ![nikitachauhan_0-1738064641771.png](https://global.discourse-cdn.com/dynatrace/original/3X/4/1/410b4d13a7f4dc7550824d9e1330cd2f9b092332.png)

**2. Verify the alert profile configuration**

Ensure that the alert profile configured in Dynatrace to trigger notifications is linked to the problem.

For example, my alert profile is “JT”.

 ![nikitachauhan_2-1738064823361.png](https://global.discourse-cdn.com/dynatrace/original/2X/f/f10bec377f4e8605322ea2a00b707110bf1b511f.png)

**3. Use Data Explorer**

Go to Data Explorer and select the metric “Server - Notifications - Problem Notifications (dsfm:server.notifications.problem\_notifications)”. Filter the concerned notification configuration to find out if there was any error while sending the notification.

 ![nikitachauhan_3-1738065590867.png](https://global.discourse-cdn.com/dynatrace/original/3X/6/a/6a37bc6858de6d628f73f9c7835cb0b351f35999.png)

Other valuable dimensions (notification.type,&nbsp;notification.display\_name,&nbsp;notification.reason,&nbsp;http\_status\_code,&nbsp;alerting\_profile.display\_name,&nbsp;executed\_retries,&nbsp;notification.delivery\_status,&nbsp;http\_status\_class,&nbsp;notification.id,&nbsp;alerting\_profile.id,&nbsp;will\_retry,&nbsp;problem.status)

More details can be viewed from the preset Dashboard:&nbsp;_Davis® health self-monitoring_

 ![nikitachauhan_0-1738148066123.png](https://global.discourse-cdn.com/dynatrace/original/1X/b788de771754d3d7200f5f70a17e4279d138da9f.png)

**4. For Managed clusters, you can also**

Download the Cluster support archive and search for the file named “audit.notifications._0_.log” (\SupportArchive\*.zip\SERVER\<nodeId\>\logs). Search using the Problem ID in the logs to find the corresponding log entry.

```markup
2025-01-28 10:46:57 UTC {"eventType":"SEND","tenantId":"kqu***","userId":"Notification service","userIdType":"SERVICE_NAME","userOrigination":"Notification service (Internal)","sessionId":null,"identity":"P-25019141","identityCategory":"NOTIFICATION","success":false,"timestamp":1738061217224,"message":"distributorType: SERVICE_NOW_EVENT tenantUuid: kqu*** integrationConfigId: 8 ********98 alertingProfileConfigId: c********** 2 reasons: [NEW, NEW_EVENT] status: OPEN problemId: 5970829412515165095_1738060980000V2 nRetries: 0 willRetry: false callDuration: PT0.318733069Sresult: NotificationResult [retryRecommended=false, message=Invalid status code., exception=, deliveryStatus=INVALID_HTTP_STATUS_CODE, response=NotificationResponse [httpStatusCode=404, body={\"success\":false,\"error\":{\"message\":\"Token \\\"c********6\\\" not found\",\"id\":\"\"}}], uri=https://webhook.site/c******6/api/global/em/jsonv2, suppressed=[]]","jsonPatch":null}

```

Note: The logs are present on any one of the nodes, so please check all server files.

Retries: we do&nbsp;3 retries if the notification is not sent.(The retry strategy (which error codes, interval, retry count) is hardcoded per notification type and can’t be configured.)

## Resolution

Once you get the error code based on it, you can continue troubleshooting it with your internal incident management/ middleware team.

## What’s next

If you’re still unable to find the issue, please create a ticket with the Dynatrace Support team, including the link to the problem ID and notification profile.