Skip to content

Commit a0eacfe

Browse files
authored
Update for github issue
------- cc: @rboucher
1 parent dd827b5 commit a0eacfe

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/azure-monitor/essentials/diagnostic-settings.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: rboucher
55
ms.author: robb
66
services: azure-monitor
77
ms.topic: conceptual
8-
ms.date: 03/07/2022
8+
ms.date: 09/30/2022
99
ms.reviewer: lualderm
1010
---
1111

@@ -88,6 +88,12 @@ The activity log uses a diagnostic setting but has its own user interface becaus
8888

8989
This section discusses requirements and limitations.
9090

91+
### Time before telemetry gets to destination
92+
93+
Once you have set up a diagnostic setting, data should start flowing to your selected destination(s) with 90 minutes. If you get no information within 24 hours, then either
94+
- no logs are being generated or
95+
- something is wrong in the underlying routing mechanism. Try disabling the configuration and then reenabling it. Contact Azure support through the Azure portal if you continue to have issues.
96+
9197
### Metrics as a source
9298

9399
There are certain limitations with exporting metrics:

0 commit comments

Comments
 (0)