Merge pull request #259888 from pdjokar96/troubleshoot-log-forwarding

Updating troubleshooting guide to capture resource lock scenario

Author: prmerger-automator[bot]

articles/partner-solutions/datadog/troubleshoot.md

@@ -75,6 +75,10 @@ The Azure Datadog integration provides you with the ability to install Datadog a
 
 If the Datadog agent is configured with an incorrect key, navigate to the API keys screen and change the **Default Key**. You must uninstall the Datadog agent and reinstall it to configure the virtual machine with the new API keys.
 
+## Diagnostic settings are active even after disabling the Datadog resource or applying necessary tag rules
+
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the Datadog resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) 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, 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.
+
 ## Next steps
 
 - Learn about [managing your instance](manage.md) of Datadog.

articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md

@@ -55,6 +55,10 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
 
 - To collect metrics, you must have owner permission on the subscription. If you're a contributor, refer to the contributor guide mentioned in [Configure metrics and logs](dynatrace-create.md#configure-metrics-and-logs).
 
+### Diagnostic settings are active even after disabling the Dynatrace resource or applying necessary tag rules
+
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the Dynatrace resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) 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, remove the delete lock from the resource or the resource group. If the lock is removed after the Dynatrace resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
+
 ### Free trial errors
 
 - **Unable to create another free trial resource on Azure**

articles/partner-solutions/elastic/troubleshoot.md

@@ -30,6 +30,10 @@ Only users who have *Owner* or *Contributor* access on the Azure subscription ca
 
 - Export of Metrics data isn't supported currently by the partner solutions under Azure Monitor diagnostic settings.
 
+## Diagnostic settings are active even after disabling the Elastic resource or applying necessary tag rules
+
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the Elastic resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) 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, remove the delete lock from the resource or the resource group. If the lock is removed after the Elastic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
+
 ## Marketplace Purchase errors
 
 [!INCLUDE [marketplace-purchase-errors](../includes/marketplace-purchase-errors.md)]

articles/partner-solutions/new-relic/new-relic-troubleshoot.md

@@ -50,6 +50,10 @@ If your Azure subscription is suspended or deleted because of payment-related is
 
 New Relic manages the APIs for creating and managing resources, and for the storage and processing of customer telemetry data. The New Relic APIs might be on or outside Azure. If your Azure subscription and resource are working correctly but the New Relic portal shows problems with monitoring data, contact New Relic support.
 
+### Diagnostic settings are active even after disabling the New Relic resource or applying necessary tag rules
+
+If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules have been modified to exclude certain resources, it's likely that there's a delete lock applied to the resource(s) 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, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
+
 ## Next steps
 
 - [Manage Azure Native New Relic Service](new-relic-how-to-manage.md)