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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,12 +11,12 @@ ms.author: spelluru
11
11
---
12
12
13
13
# Diagnostic logs for an Azure event grid topic
14
-
Diagnostic Settings now allows Event Grid users to capture and view **publish and delivery failure** Logs in either a Storage account, an event hub or a Log Analytics Workspace. This article provides step-by-step instructions to enable these settings on an Event Grid Topic.
14
+
Diagnostic Settings now allow Event Grid users to capture and view **publish and delivery failure** Logs in either a Storage account, an event hub or a Log Analytics Workspace. This article provides step-by-step instructions to enable these settings on an Event Grid Topic.
15
15
16
16
## Prerequisites
17
17
18
18
- A provisioned event grid topic
19
-
- A provisioned destination for capturing diagnostic logs. It can one of the following destinations in the same location as the Event Grid topic:
19
+
- A provisioned destination for capturing diagnostic logs. It can one of the following destinations in the same location as the event grid topic:
20
20
- Azure storage account
21
21
- Event hub
22
22
- Log Analytics workspace
@@ -52,7 +52,7 @@ Diagnostic Settings now allows Event Grid users to capture and view **publish an
52
52
1. Once you enable a storage account as a capture destination and Event Grid starts emitting diagnostic logs, you should see new containers named **insights-logs-deliveryfailures** and **insights-logs-publishfailures** in the storage account.
53
53
54
54

55
-
2. As you navigate through one of the containers, you will end up at a blob in JSON format. The file contains a 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.
55
+
2. As you navigate through one of the containers, you will 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.
56
56
57
57

58
58
3. You should see content in the JSON file similar to the following example:
@@ -68,7 +68,7 @@ Diagnostic Settings now allows Event Grid users to capture and view **publish an
0 commit comments