Skip to content

Commit 3bad80e

Browse files
committed
added schemas for other types of logs
1 parent c0c7b54 commit 3bad80e

File tree

1 file changed

+69
-2
lines changed

1 file changed

+69
-2
lines changed

articles/event-hubs/event-hubs-diagnostic-logs.md

Lines changed: 69 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ You can view two types of logs for Azure Event Hubs:
2626
* **[Activity logs](../azure-monitor/platform/platform-logs-overview.md)**: These logs have information about operations performed on a job. The logs are always enabled.
2727
* **[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.
2828

29+
2930
## Enable diagnostic logs
3031

3132
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:
6364

6465
All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
6566

66-
### Archive logs schema
67+
## Archive logs schema
6768

6869
Archive log JSON strings include elements listed in the following table:
6970

@@ -101,7 +102,7 @@ The following code is an example of an archive log JSON string:
101102
}
102103
```
103104

104-
### Operational logs schema
105+
## Operational logs schema
105106

106107
Operational log JSON strings include elements listed in the following table:
107108

@@ -134,6 +135,72 @@ Example:
134135
}
135136
```
136137

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 |
173+
174+
## Event Hubs virtual network (VNet) connection event schema
175+
176+
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+
137204
## Next steps
138205
- [Introduction to Event Hubs](event-hubs-what-is-event-hubs.md)
139206
- [Event Hubs API overview](event-hubs-api-overview.md)

0 commit comments

Comments
 (0)