Skip to content

Commit 5a7f18d

Browse files
Update troubleshoot.md
1 parent 3dd84a9 commit 5a7f18d

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,6 @@ If logs are being emitted and diagnostic settings remain active on monitored res
5050

5151
If logs are being emitted even after the Azure Native New Relic resource is deleted, it could be because there is a resource lock present on one of the Azure resources being monitored. It will take 24 hours for the log forwarding to stop for the resources where the resource lock is present.
5252

53-
## Any updates made to the tag rules within the Azure Native New Relic resource doesn't change the log flow immediately
53+
## Updates made to the tag rules within the Azure Native New Relic resource don't change the log flow immediately
5454

5555
It takes an hour for any modification of the tag rules to reflect in the log flow. For example, if a new resource is added in tag rules, it would take an hour for the log forwarding to start for that particular resource

0 commit comments

Comments
 (0)