Skip to content

Commit c860708

Browse files
Update diagnostic-settings-manual-update.md
1 parent 30a4c0a commit c860708

1 file changed

Lines changed: 4 additions & 5 deletions

File tree

support/azure/partner-solutions/diagnostic-settings-manual-update.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,20 +15,19 @@ This article explains the behavior and limitations when attempting to manually u
1515

1616
## Symptoms
1717

18-
- Changes made to log categories in the diagnostic settings page do not persist.
18+
- Changes made to log categories in the diagnostic settings page don't persist.
1919
- Unchecked log categories revert to their default settings after saving.
2020
- Modifying destination details results in a new diagnostic setting being created with the original configuration.
21-
- Unable to customize diagnostic settings beyond what is defined by tag rules.
21+
- Unable to customize diagnostic settings other than those defined by tag rules.
2222

2323
## Cause
2424

25-
Diagnostic settings created via tag rules are managed automatically. Manual changes to log categories through the Azure portal are not supported. Even if you uncheck log categories and save, the settings will revert to the defaults specified by the tag rules. If you modify destination details, a new diagnostic setting is created with the original configuration, subject to the Azure limitation of a maximum of five diagnostic settings per resource.
25+
Diagnostic settings created via tag rules are managed automatically. Manual changes to log categories through the Azure portal aren't supported. Even if you uncheck log categories and save, the settings will revert to the defaults specified by the tag rules. If you modify destination details, a new diagnostic setting is created with the original configuration, subject to the Azure limitation of a maximum of five diagnostic settings per resource.
2626

2727
## Solution
2828

29-
- Be aware that manual changes to log categories in diagnostic settings managed by tag rules will not persist.
3029
- To change the configuration, update the tag rules that govern the diagnostic settings.
31-
- If you need to modify destination details, ensure you do not exceed the maximum of five diagnostic settings per resource.
30+
- If you need to modify destination details, ensure you don't exceed the maximum of five diagnostic settings per resource.
3231

3332
> [!TIP]
3433
> For more information about diagnostic settings and tag rules, see [Create diagnostic settings in Azure](/azure/azure-monitor/essentials/diagnostic-settings).

0 commit comments

Comments
 (0)