Skip to content

Commit d199896

Browse files
committed
fixed based on feedback from Samarth
1 parent ea38ed6 commit d199896

File tree

2 files changed

+13
-11
lines changed

2 files changed

+13
-11
lines changed

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

Lines changed: 12 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Event Grid - Enable diagnostic logs for a topic
2+
title: Azure Event Grid - Enable diagnostic logs for topics or domains
33
description: This article provides step-by-step instructions on how to enable diagnostic logs for an Azure event grid topic.
44
services: event-grid
55
author: spelluru
@@ -10,7 +10,7 @@ ms.date: 04/27/2020
1010
ms.author: spelluru
1111
---
1212

13-
# Diagnostic logs for an Azure event grid topic
13+
# Enable Diagnostic logs for an Azure event grid topics or domains
1414
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
@@ -21,9 +21,11 @@ Diagnostic Settings now allow Event Grid users to capture and view **publish and
2121
- Event hub
2222
- Log Analytics workspace
2323

24-
2524
## Steps for enabling diagnostic logs for a topic
2625

26+
> [!NOTE]
27+
> The following procedure provides step-by-step instructions for enabling diagnostic logs for a topic. Steps for enabling diagnostic logs for a domain are very similar. You navigate to the event grid domain in the Azure portal and follow step 3 onwards.
28+
2729
1. Sign in to the [Azure portal](https://portal.azure.com).
2830
2. Navigate to the event grid topic for which you want to enable diagnostic log settings.
2931
3. Select **Diagnostic settings** under **Monitoring** in the left menu.
@@ -68,16 +70,16 @@ Diagnostic Settings now allow Event Grid users to capture and view **publish and
6870
}
6971
```
7072

71-
## Publish and delivery failure log schema
73+
## Schema for publish/delivery failure logs
7274

7375
| Property name | Data type | Description |
7476
| ------------- | --------- | ----------- |
75-
| Time | DateTime | Time when the log entry was generated <p>**Example value:** 01-29-2020 09:52:02.700</p> |
76-
| EventSubscriptionName | String | Name of the event subscription <p>**Example value:** "EVENTSUB1"</p> <p>This property exists only for delivery failure logs.</p> |
77-
| Category | String | Log category name. <p>**Example values:** "DeliveryFailures" or "PublishFailures" |
78-
| OperationName | String | Name of the operation performed while encountering the failure.<p>**Example Values:** "Deliver" for delivery failures. |
79-
| Message | String | Log message for the user explaining the reason for the failure and other additional details. |
80-
| ResourceId | String | ResourceId for the topic/domain resource<p>**Example Values:** `/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID/RESOURCEGROUPS/SAMPLE-RESOURCEGROUP/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/TOPIC1` |
77+
| Time | DateTime | The time when the log entry was generated <p>**Example value:** 01-29-2020 09:52:02.700</p> |
78+
| EventSubscriptionName | String | The name of the event subscription <p>**Example value:** "EVENTSUB1"</p> <p>This property exists only for delivery failure logs.</p> |
79+
| Category | String | The log category name. <p>**Example values:** "DeliveryFailures" or "PublishFailures" |
80+
| OperationName | String | The name of the operation performed while encountering the failure.<p>**Example Values:** "Deliver" for delivery failures. |
81+
| Message | String | The log message for the user explaining the reason for the failure and other additional details. |
82+
| ResourceId | String | The resource ID for the topic/domain resource<p>**Example Values:** `/SUBSCRIPTIONS/SAMPLE-SUBSCRIPTION-ID/RESOURCEGROUPS/SAMPLE-RESOURCEGROUP/PROVIDERS/MICROSOFT.EVENTGRID/TOPICS/TOPIC1` |
8183

8284
## Next steps
8385
See the following article: [Create diagnostic setting to collect resource logs and metrics in Azure](../azure-monitor/platform/diagnostic-settings.md)

articles/event-grid/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -193,7 +193,7 @@
193193
href: custom-disaster-recovery.md
194194
- name: Troubleshoot
195195
items:
196-
- name: Enable diagnostic logs for a topic
196+
- name: Enable diagnostic logs
197197
href: enable-diagnostic-logs-topic.md
198198
- name: Troubleshoot errors
199199
href: troubleshoot-errors.md

0 commit comments

Comments
 (0)