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-hubs/event-hubs-diagnostic-logs.md
+40-38Lines changed: 40 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,8 +26,8 @@ You can view two types of logs for Azure Event Hubs:
26
26
***[Activity logs](../azure-monitor/platform/platform-logs-overview.md)**: These logs have information about operations done on a job. The logs are always enabled. You can see activity log entries by selecting **Activity log** in the left pane for your event hub namespace in the Azure portal. For example: "Create or Update Namespace", "Create or Update Event Hub".
27
27
28
28
29
-
***[Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md)**: You can configure diagnostic logs for a richer view of everything that happens with a job. Diagnostic logs cover activities from the time the job is created until the job is deleted, including updates and activities that occur while the job is running.
30
-
29
+
***[Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md)**: Diagnostic logs provide richer information about operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK.
30
+
31
31
The following section shows you how to enable diagnostic logs for an Event Hubs namespace.
32
32
33
33
## Enable diagnostic logs
@@ -51,45 +51,47 @@ Diagnostic logs are disabled by default. To enable diagnostic logs, follow these
51
51
52
52
Event Hubs captures diagnostic logs for the following categories:
53
53
54
-
-**Archive Logs**: logs related to Event Hubs archives, specifically, logs related to archive errors.
55
-
-**Operational Logs**: information about what is happening during Event Hubs operations, specifically, the operation type, including event hub creation, resources used, and the status of the operation.
56
-
-**Auto scale logs**: information about autoscaling operations done on an Event Hubs namespace.
57
-
-**Kafka coordinator logs** - information about Kafka coordinator operations related to Event Hubs.
58
-
-**Kafka user logs**: information about Kafka user operations related to Event Hubs.
59
-
-**Event Hubs virtual network (VNet) connection event**: information about Event Hubs virtual network connection events.
60
-
-**Customer-managed key user logs**: information about operations related to customer-managed key.
54
+
| Category | Description |
55
+
| -------- | ----------- |
56
+
| Archive Logs | Captures information about [Event Hubs Capture](event-hubs-capture-overview.md) operations, specifically, logs related to capture errors. |
57
+
| Operational Logs | Capture all management operations that are performed on the Azure Event Hubs namespace. Data operations are not captured, because of the high volume of data operations that are conducted on Azure Event Hubs. |
58
+
| Auto scale logs | Captures auto-inflate operations done on an Event Hubs namespace. |
59
+
| Kafka coordinator logs | Captures Kafka coordinator operations related to Event Hubs. |
60
+
| Kafka user error logs | Captures information about Kafka APIs called on Event Hubs. |
61
+
| Event Hubs virtual network (VNet) connection event | Captures information about IP addresses and virtual networks sending traffic to Event Hubs. |
62
+
| Customer-managed key user logs | Captures operations related to customer-managed key. |
61
63
62
64
63
-
All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
65
+
All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
64
66
65
67
## Archive logs schema
66
68
67
69
Archive log JSON strings include elements listed in the following table:
68
70
69
71
Name | Description
70
72
------- | -------
71
-
TaskName | Description of the task that failed.
72
-
ActivityId | Internal ID, used for tracking.
73
-
trackingId | Internal ID, used for tracking.
74
-
resourceId | Azure Resource Manager resource ID.
75
-
eventHub | Event hub full name (includes namespace name).
76
-
partitionId | Event Hub partition being written to.
77
-
archiveStep | ArchiveFlushWriter
78
-
startTime | Failure start time.
79
-
failures | Number of times failure occurred.
80
-
durationInSeconds | Duration of failure.
81
-
message | Error message.
73
+
TaskName | Description of the task that failed
74
+
ActivityId | Internal ID, used for tracking
75
+
trackingId | Internal ID, used for tracking
76
+
resourceId | Azure Resource Manager resource ID
77
+
eventHub | Event hub full name (includes namespace name)
78
+
partitionId | Event Hub partition being written to
79
+
archiveStep | possible values: ArchiveFlushWriter, DestinationInit
80
+
startTime | Failure start time
81
+
failures | Number of times the failure occurred
82
+
durationInSeconds | Duration of failure
83
+
message | Error message
82
84
category | ArchiveLogs
83
85
84
86
The following code is an example of an archive log JSON string:
0 commit comments