You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-grid/enable-diagnostic-logs-topic.md
+19-19Lines changed: 19 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,49 +54,49 @@ This article provides step-by-step instructions for enabling diagnostic settings
54
54
- If you select **Archive to a storage account**, select **Storage account - Configure**, and then select the storage account in your Azure subscription.
55
55
56
56
:::image type="content" source="./media/enable-diagnostic-logs-topic/archive-storage.png" alt-text="Screenshot that shows the Diagnostic settings page with Archive to an Azure storage account checked and a storage account selected.":::
57
-
- If you select **Stream to an event hub**, select **Event hub - Configure**, and then select the Event Hubs namespace, event hub, and the access policy.
58
-
59
-
57
+
- If you select **Stream to an event hub**, select **Event hub - Configure**, and then select the Event Hubs namespace, event hub, and the access policy.
58
+
59
+
60
60
1. Select **Save**. Then, select **X** in the right-corner to close the page.
61
61
1. Now, back on the **Diagnostic settings** page, confirm that you see a new entry in the **Diagnostics Settings** table.
62
62
63
63
64
-
64
+
65
65
You can also enable collection of all metrics for the topic.
66
66
67
67
## Enable diagnostic logs for Event Grid system topics
68
68
69
69
1. Sign in to the [Azure portal](https://portal.azure.com).
70
-
2. Navigate to the system topic for which you want to enable diagnostic log settings.
70
+
1. Navigate to the system topic for which you want to enable diagnostic log settings.
71
71
1. In the search bar at the top, search for **Event Grid system topics**.
72
72
73
-
1. Select the **system topic** for which you want to configure diagnostic settings.
74
-
75
-
3. Select **Diagnostic settings** under **Monitoring** on the left menu, and then select **Add diagnostic setting**.
1. Enable one or more of the capture destinations for the logs, and then configure them by selecting a previous created capture resource.
81
81
- If you select **Send to Log Analytics**, select the Log Analytics workspace.
82
82
83
-
- If you select **Archive to a storage account**, select **Storage account - Configure**, and then select the storage account in your Azure subscription.
84
-
83
+
- If you select **Archive to a storage account**, select **Storage account - Configure**, and then select the storage account in your Azure subscription.
84
+
85
85
- If you select **Stream to an Event Hub**, select **Event Hub - Configure**, and then select the Event Hubs namespace, event hub, and the access policy.
86
86
87
87
7. Select **Save**. Then, select **X** in the right-corner to close the page.
88
-
8. Now, back on the **Diagnostic settings** page, confirm that you see a new entry in the **Diagnostics Settings** table.
89
-
88
+
1. Now, back on the **Diagnostic settings** page, confirm that you see a new entry in the **Diagnostics Settings** table.
89
+
90
90
91
91
You can also enable collection of all **metrics** for the system topic.
92
-
92
+
93
93
94
94
## View diagnostic logs in Azure Storage
95
95
96
96
1. Once you enable a storage account as a capture destination, Event Grid starts emitting diagnostic logs. You should see new containers named **insights-logs-deliveryfailures** and **insights-logs-publishfailures** in the storage account.
97
97
98
98
99
-
2. As you navigate through one of the containers, you'll end up at a blob in JSON format. The file contains log entries for either a delivery failure or a publish failure. The navigation path represents the **ResourceId** of the Event Grid topic and the timestamp (minute level) as to when the log entries were emitted. The blob/JSON file, which is downloadable, in the end adheres to the schema described in the next section.
99
+
1. As you navigate through one of the containers, you'll end up at a blob in JSON format. The file contains log entries for either a delivery failure or a publish failure. The navigation path represents the **ResourceId** of the Event Grid topic and the timestamp (minute level) as to when the log entries were emitted. The blob/JSON file, which is downloadable, in the end adheres to the schema described in the next section.
100
100
101
101
102
102
3. You should see content in the JSON file similar to the following example:
@@ -218,4 +218,4 @@ The audit trace can be used to ensure that data access is allowed only for autho
218
218
219
219
## Next steps
220
220
221
-
For the log schema and other conceptual information about diagnostic logs for topics or domains, see [Diagnostic logs](monitor-push-reference.md).
221
+
For the log schema and other conceptual information about diagnostic logs for topics or domains, see [Diagnostic logs](monitor-push-reference.md#schema-for-data-plane-operations-logs).
![prmerger-automator[bot]](https://avatars.githubusercontent.com/u/22479449?v=4&size=40){kind=avatar}
0 commit comments