Skip to content

Commit 1db54b0

Browse files
Merge pull request #280307 from neilghuman/cosmos-db-diagnostic-logs-add-warning
cosmos-db-diagnostic-logs-add-warning
2 parents 05191b1 + 3265d1e commit 1db54b0

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

articles/cosmos-db/monitor-resource-logs.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,11 @@ Platform metrics and the Activity logs are collected automatically, whereas you
3535
- Alternatively, you can [try Azure Cosmos DB free](try-free.md) before you commit.
3636
- An existing Azure Monitor Log Analytics workspace.
3737

38+
> [!WARNING]
39+
> 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.
40+
>
41+
> 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.
42+
3843
## Create diagnostic settings
3944

4045
Here, we walk through the process of creating diagnostic settings for your account.

0 commit comments

Comments
 (0)