Skip to content

Commit f50e7ae

Browse files
authored
Update troubleshoot.md
1 parent aae7136 commit f50e7ae

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/partner-solutions/datadog/troubleshoot.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -73,6 +73,8 @@ If the Datadog agent is configured with an incorrect key, navigate to the API ke
7373

7474
If logs are being emitted and diagnostic settings remain active on monitored resources even after the Datadog resource is disabled or tag rules are modified to exclude certain resources, it's likely that there's a delete lock applied to the resources or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve this issue, remove the delete lock from the resource or the resource group. If the lock is removed after the Datadog resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
7575

76+
[!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
77+
7678
## Next steps
7779

7880
- Learn about [managing your instance](manage.md) of Datadog.

0 commit comments

Comments
 (0)