Update create-diagnostic-settings.md #179
Conversation
Adding update to reflect the following known issue and considerations to avoid unexpected billing due loop ingestion issues. > From Azure portal when creating or updating Diagnostic Settings for an Azure Storage account or Azure Event Hub namespace, you could be unable to select itself as a destination for the resource logs or metrics data. > This is by design as it is possible to get into a state where resource logs or metrics being sent from a resource to the same resource would generate an infinite loop of generating and writing data. > This design is only applied at the Azure portal UX layer, if there is truly a need to write data to the same resource and you are willing to accept the associated risks, you can create the Diagnostic Setting using Azure PowerShell, Azure CLI, REST API, ARM Template or other supported Microsoft SDK.
|
Learn Build status updates of commit 1097398:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/azure-monitor/platform/create-diagnostic-settings.md | Details |
articles/azure-monitor/platform/create-diagnostic-settings.md
- Line 56, Column 1: [Warning: code-block-indented - See documentation]
Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
|
This pull request has been inactive for at least 14 days. If you are finished with your changes, don't forget to sign off. See the contributor guide for instructions. |
|
@bwren, do you have any update maybe? |
|
@miguel-parada The article has been deleted and now redirects to Diagnostic settings in Azure Monitor, and this change no longer applies. If you'd still like to update the article, please open a new PR. Or if you believe this PR was closed by mistake, email the PublicPRs alias. #please-close |
|
done :) #185 |
Adding update to reflect the following known issue and considerations to avoid unexpected billing due loop ingestion issues.