Skip to content

Commit c93f976

Browse files
committed
acrolynx
1 parent c4b2a6c commit c93f976

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/event-grid/enable-diagnostic-logs-topic.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,12 @@ ms.author: spelluru
1111
---
1212

1313
# 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.
1515

1616
## Prerequisites
1717

1818
- 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:
2020
- Azure storage account
2121
- Event hub
2222
- Log Analytics workspace
@@ -52,7 +52,7 @@ Diagnostic Settings now allows Event Grid users to capture and view **publish an
5252
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.
5353

5454
![Storage - containers for diagnostic logs](./media/enable-diagnostic-logs-topic/storage-containers.png)
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.
5656

5757
![JSON file in the storage](./media/enable-diagnostic-logs-topic/select-json.png)
5858
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
6868
}
6969
```
7070

71-
## Pubish and delivery failure log schema
71+
## Publish and delivery failure log schema
7272

7373
| Property name | Data type | Description |
7474
| ------------- | --------- | ----------- |

0 commit comments

Comments
 (0)