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
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Azure Event Grid - Enable diagnostic logs for a topic
2
+
title: Azure Event Grid - Enable diagnostic logs for topics or domains
3
3
description: This article provides step-by-step instructions on how to enable diagnostic logs for an Azure event grid topic.
4
4
services: event-grid
5
5
author: spelluru
@@ -10,7 +10,7 @@ ms.date: 04/27/2020
10
10
ms.author: spelluru
11
11
---
12
12
13
-
# Diagnostic logs for an Azure event grid topic
13
+
# Enable Diagnostic logs for an Azure event grid topics or domains
14
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
@@ -21,9 +21,11 @@ Diagnostic Settings now allow Event Grid users to capture and view **publish and
21
21
- Event hub
22
22
- Log Analytics workspace
23
23
24
-
25
24
## Steps for enabling diagnostic logs for a topic
26
25
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
+
27
29
1. Sign in to the [Azure portal](https://portal.azure.com).
28
30
2. Navigate to the event grid topic for which you want to enable diagnostic log settings.
29
31
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
68
70
}
69
71
```
70
72
71
-
## Publish and delivery failure log schema
73
+
## Schema for publish/delivery failure logs
72
74
73
75
| Property name | Data type | Description |
74
76
| ------------- | --------- | ----------- |
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> |
| 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` |
81
83
82
84
## Next steps
83
85
See the following article: [Create diagnostic setting to collect resource logs and metrics in Azure](../azure-monitor/platform/diagnostic-settings.md)
0 commit comments