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
+69-2Lines changed: 69 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,6 +26,7 @@ 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 performed on a job. The logs are always enabled.
27
27
***[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.
28
28
29
+
29
30
## Enable diagnostic logs
30
31
31
32
Diagnostic logs are disabled by default. To enable diagnostic logs, follow these steps:
@@ -63,7 +64,7 @@ Event Hubs captures diagnostic logs for two categories:
63
64
64
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.
65
66
66
-
###Archive logs schema
67
+
## Archive logs schema
67
68
68
69
Archive log JSON strings include elements listed in the following table:
69
70
@@ -101,7 +102,7 @@ The following code is an example of an archive log JSON string:
101
102
}
102
103
```
103
104
104
-
###Operational logs schema
105
+
## Operational logs schema
105
106
106
107
Operational log JSON strings include elements listed in the following table:
107
108
@@ -134,6 +135,72 @@ Example:
134
135
}
135
136
```
136
137
138
+
## Autoscale logs schema
139
+
Autoscale log JSON includes elements listed in the following table:
140
+
141
+
| Name | Description |
142
+
| ---- | ----------- |
143
+
| trackingId | Internal ID, which is used for tracing purposes |
144
+
| resourceId | Internal ID, which contains Azure subscription ID and namespace name |
145
+
| message | Informational message, which provides details about auto-inflate action. The message contains previous and current value of throughput unit for a given namespace and what triggered the inflate of the TU. |
146
+
147
+
## Kafka coordinator logs schema
148
+
Kafka coordinator log JSON includes elements listed in the following table:
149
+
150
+
| Name | Description |
151
+
| ---- | ----------- |
152
+
| requestId | request ID, which is used for tracing purposes |
153
+
| resourceId | Internal ID, which contains Azure subscription ID and namespace name |
154
+
| operationName | Name of the operation that's performed during the group coordination |
155
+
| clientId | Client ID |
156
+
| namespaceName | Namespace name |
157
+
| subscriptionId | Azure subscription ID |
158
+
| message | Informational message, which provides details about actions performed during the consumer group coordination. |
159
+
160
+
## Kafka user error logs schema
161
+
Kafka user error log JSON includes elements listed in the following table:
162
+
163
+
| Name | Description |
164
+
| ---- | ----------- |
165
+
| trackingId | tracking ID, which is used for tracing purposes. |
166
+
| namespaceName | Namespace name |
167
+
| eventhub | Event hub name |
168
+
| partitionId | Partition ID |
169
+
| groupId | Group ID |
170
+
| ClientId | Client ID |
171
+
| resourceId | Internal ID, which contains Azure subscription ID and namespace name |
172
+
| message | Informational message, which provides details about an error |
Event Hubs virtual network (VNet) connection event JSON includes elements listed in the following table:
177
+
178
+
| Name | Description |
179
+
| --- | ----------- |
180
+
| subscriptionId | Azure subscription ID |
181
+
| namespaceName | Namespace name |
182
+
| ipAddress | IP address of a client connecting to the Event Hubs service |
183
+
| action | Action performed by the Event Hubs service when evaluating connection requests. Supported actions are **AcceptConnection** and **RejectConnection**. |
184
+
| reason | Provides a reason why the action was done |
185
+
| count | Number of occurrences for the given action |
186
+
| resourceId | Internal resource ID, which contains subscription ID and namespace name. |
187
+
188
+
## Customer-managed key user logs
189
+
Customer-managed key user log JSON includes elements listed in the following table:
190
+
191
+
| Name | Description |
192
+
| ---- | ----------- |
193
+
| category | Type of category for a message. It's one of the following values: **error** and **info**|
194
+
| resourceId | Internal resource ID, which includes Azure subscription ID and namespace name |
195
+
| keyVault | Name of the Key Vault resource |
196
+
| key | Name of the Key Vault key. |
197
+
| version | Version of the Key Vault key |
198
+
| operation | The name of an operation performed to serve requests |
199
+
| code | Status code |
200
+
| message | Message, which provides details about an error or informational message |
201
+
202
+
203
+
137
204
## Next steps
138
205
-[Introduction to Event Hubs](event-hubs-what-is-event-hubs.md)
139
206
-[Event Hubs API overview](event-hubs-api-overview.md)
0 commit comments