Merge pull request #292375 from agrimayadav/updated-diagnostic-settings-vF

Updated Diagnostic Settings in troubleshooting guide

Author: ttorble

articles/partner-solutions/datadog/troubleshoot.md

@@ -73,6 +73,8 @@ If the Datadog agent is configured with an incorrect key, navigate to the API ke
 
 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.
 
+[!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
+
 ## Next steps
 
 - Learn about [managing your instance](manage.md) of Datadog.

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

@@ -49,6 +49,8 @@ If those options don't solve the problem, contact [Dynatrace support](https://s
 
 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.
 
+[!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
+
 ## Free trial errors
 
 - **Unable to create another free trial resource on Azure**

articles/partner-solutions/elastic/troubleshoot.md

@@ -34,6 +34,8 @@ Only users who have *Owner* or *Contributor* access on the Azure subscription ca
 
 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.
 
+[!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
+
 ## Marketplace Purchase errors
 
 [!INCLUDE [marketplace-purchase-errors](../includes/marketplace-purchase-errors.md)]

articles/partner-solutions/includes/diagnostic-settings.md

@@ -0,0 +1,15 @@
+---
+author: agrimayadav
+ms.topic: include
+ms.date: 12/16/2024
+ms.author: agrimayadav
+---
+## Diagnostic settings not created as expected after moving a resource
+
+If you need to delete a resource, rename, or move a resource, or migrate it across resource groups or subscriptions, first delete its diagnostic settings. Otherwise, if you recreate this resource, the diagnostic settings for the deleted resource could be included with the new resource, depending on the resource configuration for each resource. If the diagnostics settings are included with the new resource, this resumes the collection of resource logs as defined in the diagnostic setting and sends the applicable metric and log data to the previously configured destination. Also, it's a good practice to delete the diagnostic settings for a resource you're going to delete and don't plan on using again to keep your environment clean. [Learn more](/azure/azure-monitor/essentials/diagnostic-settings)
+
+## Manual updates to diagnostic settings created via tag rules
+
+Diagnostic settings are created based on tag rules. Currently, modifying log categories through the diagnostic settings page is not permitted. While you may be able to uncheck log categories and save them, they will revert to default settings (as per tag rules).
+
+If destination details are modified, a new diagnostic setting with the original configuration is recreated. This is subject to the limitation of a maximum of five diagnostic settings per resource. [Learn More](/azure/azure-monitor/essentials/diagnostic-settings)

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

@@ -34,7 +34,7 @@ Only virtual machines that currently have the New Relic agent installed should b
 
 ## Resource monitoring stopped working
 
-Resource monitoring in New Relic is enabled through the *ingest API key*, which you set up at the time of resource creation. Revoking the ingest API key from the New Relic portal disrupts monitoring of logs and metrics for all resources, including virtual machines and app services. You shouldn't* revoke the ingest API key. If the API key is already revoked, contact New Relic support.
+Resource monitoring in New Relic is enabled through the *ingest API key*, which you set up at the time of resource creation. Revoking the ingest API key from the New Relic portal disrupts monitoring of logs and metrics for all resources, including virtual machines and app services. You shouldn't revoke the ingest API key. If the API key is already revoked, contact New Relic support.
 
 If your Azure subscription is suspended or deleted because of payment-related issues, resource monitoring in New Relic automatically stops. Use a different Azure subscription. Or, add or update the credit card or payment method for the subscription. For more information, see [Add, update, or delete a payment method](../../cost-management-billing/manage/change-credit-card.md).
 
@@ -44,6 +44,8 @@ New Relic manages the APIs for creating and managing resources, and for the stor
 
 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.
 
+[!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
+
 ## Next steps
 
 - [Manage Azure Native New Relic Service](new-relic-how-to-manage.md)