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
See [Monitor Azure Event Hubs](monitor-event-hubs.md) for details on the data you can collect for Event Hubs and how to use it.
38
15
39
16
Azure Event Hubs creates monitoring data using [Azure Monitor](../azure-monitor/overview.md), which is a full stack monitoring service in Azure. Azure Monitor provides a complete set of features to monitor your Azure resources. It can also monitor resources in other clouds and on-premises.
40
17
41
-
Azure Event Hubs collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](../azure-monitor/essentials/monitor-azure-resource.md#monitoring-data).
18
+
Azure Event Hubs collects the same kinds of monitoring data as other Azure resources that are described in [Monitoring data from Azure resources](../azure-monitor/essentials/monitor-azure-resource.md#monitoring-data).
### Supported metrics for Microsoft.EventHub/clusters
48
23
49
24
The following table lists the metrics available for the Microsoft.EventHub/clusters resource type.
@@ -60,59 +35,57 @@ The following table lists the metrics available for the Microsoft.EventHub/Names
60
35
61
36
This section lists all the automatically collected platform metrics collected for Azure Event Hubs. The resource provider for these metrics is `Microsoft.EventHub/clusters` or `Microsoft.EventHub/namespaces`.
62
37
63
-
### Request metrics
64
-
65
-
Counts the number of data and management operations requests.
66
-
67
-
| Metric name | Exportable via diagnostic settings | Unit | Aggregation type | Description | Dimensions |
| Incoming Requests | Yes | Count | Count | The number of requests made to the Event Hubs service over a specified period. This metric includes all the data and management plane operations. | Entity name|
70
-
| Successful Requests | No | Count | Count | The number of successful requests made to the Event Hubs service over a specified period. | Entity name<br/><br/>Operation Result |
71
-
| Throttled Requests | No | Count | Count | The number of requests that were throttled because the usage was exceeded. | Entity name<br/><br/>Operation Result |
72
-
73
-
The following two types of errors are classified as **user errors**:
38
+
Request metrics count the number of data and management operations requests. This table provides more information about values from the preceding tables.
74
39
75
-
1. Client-side errors (In HTTP that would be 400 errors).
76
-
2. Errors that occur while processing messages.
40
+
| Metric name | Description |
41
+
|:--------------------|:------------|
42
+
| Incoming Requests | The number of requests made to the Event Hubs service over a specified period. This metric includes all the data and management plane operations. |
43
+
| Successful Requests | The number of successful requests made to the Event Hubs service over a specified period. |
44
+
| Throttled Requests | The number of requests that were throttled because the usage was exceeded. |
77
45
78
-
### Message metrics
46
+
This table provides more information for message metrics from the preceding tables.
79
47
80
-
| Metric name |Exportable via diagnostic settings | Unit | Aggregation type |Description| Dimensions|
|Incoming Messages | Yes | Count | Count |The number of events or messages sent to Event Hubs over a specified period.| Entity name|
83
-
|Outgoing Messages | Yes | Count | Count |The number of events or messages received from Event Hubs over a specified period.| Entity name|
84
-
| Captured Messages |No | Count | Count |The number of captured messages. | Entity name |
85
-
|Incoming Bytes | Yes | Bytes | Count |Incoming bytes for an event hub over a specified period. | Entity name|
86
-
|Outgoing Bytes | Yes | Bytes | Count |Outgoing bytes for an event hub over a specified period. | Entity name |
87
-
| Size |No | Bytes | Average |Size of an event hub in bytes.|Entity name|
48
+
| Metric name | Description |
49
+
|:------------|:------------|
50
+
|Incoming Messages |The number of events or messages sent to Event Hubs over a specified period. |
51
+
|Outgoing Messages |The number of events or messages received from Event Hubs over a specified period. |
52
+
| Captured Messages | The number of captured messages. |
53
+
|Incoming Bytes |Incoming bytes for an event hub over a specified period. |
54
+
|Outgoing Bytes |Outgoing bytes for an event hub over a specified period. |
55
+
| Size | Size of an event hub in bytes. |
88
56
89
57
> [!NOTE]
90
58
> - These values are point-in-time values. Incoming messages that were consumed immediately after that point-in-time may not be reflected in these metrics.
91
59
> - The **Incoming requests** metric includes all the data and management plane operations. The **Incoming messages** metric gives you the total number of events that are sent to the event hub. For example, if you send a batch of 100 events to an event hub, it'll count as 1 incoming request and 100 incoming messages.
92
60
93
-
### Capture metrics
61
+
This table provides more information for capture metrics from the preceding tables.
62
+
63
+
| Metric name | Description |
64
+
|:------------|:------------|
65
+
| Captured Messages | The number of captured messages. |
66
+
| Captured Bytes | Captured bytes for an event hub. |
67
+
| Capture Backlog | Capture backlog for an event hub. |
94
68
95
-
| Metric name | Exportable via diagnostic settings | Unit | Aggregation type | Description | Dimensions |
| Captured Messages | No | Count | Count | The number of captured messages. | Entity name |
98
-
| Captured Bytes | No | Bytes | Count | Captured bytes for an event hub | Entity name |
99
-
| Capture Backlog | No | Count | Count | Capture backlog for an event hub | Entity name |
69
+
This table provides more information for connection metrics from the preceding tables.
100
70
101
-
### Connection metrics
71
+
| Metric name | Description |
72
+
|:------------|:------------|
73
+
| Active Connections | The number of active connections on a namespace and on an entity (event hub) in the namespace. Value for this metric is a point-in-time value. Connections that were active immediately after that point-in-time might not be reflected in the metric. |
74
+
| Connections Opened | The number of open connections. |
75
+
| Connections Closed | The number of closed connections. |
102
76
103
-
| Metric name | Exportable via diagnostic settings | Unit | Aggregation type | Description | Dimensions |
| Active Connections| No | Count | Average | The number of active connections on a namespace and on an entity (event hub) in the namespace. Value for this metric is a point-in-time value. Connections that were active immediately after that point-in-time might not be reflected in the metric.| Entity name |
106
-
| Connections Opened | No | Count | Average | The number of open connections. | Entity name |
107
-
| Connections Closed | No | Count | Average| The number of closed connections. | Entity name |
77
+
This table provides more information for error metrics from the preceding tables.
108
78
109
-
### Error metrics
79
+
| Metric name | Description |
80
+
|:------------|:------------|
81
+
| Server Errors | The number of requests not processed because of an error in the Event Hubs service over a specified period. |
82
+
| User Errors | The number of requests not processed because of user errors over a specified period. |
83
+
| Quota Exceeded Errors | The number of errors caused by exceeding quotas over a specified period. |
110
84
111
-
| Metric name | Exportable via diagnostic settings | Unit | Aggregation type | Description | Dimensions |
| Server Errors | No | Count | Count | The number of requests not processed because of an error in the Event Hubs service over a specified period. | Entity name<br/><br/>Operation Result |
114
-
| User Errors | No | Count | Count | The number of requests not processed because of user errors over a specified period. | Entity name<br/><br/>Operation Result |
115
-
| Quota Exceeded Errors | No | Count | Count | The number of errors caused by exceeding quotas over a specified period. | Entity name<br/><br/>Operation Result |
85
+
The following two types of errors are classified as **user errors**:
86
+
87
+
1. Client-side errors (In HTTP that would be 400 errors).
88
+
2. Errors that occur while processing messages.
116
89
117
90
> [!NOTE]
118
91
> Logic Apps creates epoch receivers and receivers may be moved from one node to another depending on the service load. During those moves, `ReceiverDisconnection` exceptions may occur. They are counted as user errors on the Event Hubs service side. Logic Apps may collect failures from Event Hubs clients so that you can view them in user logs.
@@ -121,28 +94,45 @@ The following two types of errors are classified as **user errors**:
| EntityName | Name of the event hub. With the 'Incoming Requests' metric, the Entity Name dimension has a value of '-NamespaceOnlyMetric-' in addition to all your event hubs. It represents the requests that were made at the namespace level. Examples include a request to list all event hubs in the namespace or requests to entities that failed authentication or authorization. |
100
+
| OperationResult ||
101
+
| Replica ||
102
+
| Role ||
128
103
129
-
Azure Event Hubs supports the following dimensions for metrics in Azure Monitor. Adding dimensions to your metrics is optional. If you don't add dimensions, metrics are specified at the namespace level.
104
+
Adding dimensions to your metrics is optional. If you don't add dimensions, metrics are specified at the namespace level.
130
105
131
-
| Dimension name | Description |
132
-
|:---------------|:------------|
133
-
| Entity Name | Name of the event hub. With the 'Incoming Requests' metric, the Entity Name dimension has a value of '-NamespaceOnlyMetric-' in addition to all your event hubs. It represents the requests that were made at the namespace level. Examples include a request to list all event hubs in the namespace or requests to entities that failed authentication or authorization.|
106
+
> [!NOTE]
107
+
> When you enable metrics in a diagnostic setting, dimension information is not currently included as part of the information sent to a storage account, event hub, or log analytics.
Azure Event Hubs now has the capability to dispatch logs to either of two destination tables - Azure Diagnostic or [Resource specific tables](~/articles/azure-monitor/essentials/resource-logs.md) in Log Analytics. You could use the toggle available on Azure portal to choose destination tables.
Azure Event Hubs now has the capability to dispatch logs to either of two destination tables: Azure Diagnostic or [Resource specific tables](~/articles/azure-monitor/essentials/resource-logs.md) in Log Analytics. You could use the toggle available on Azure portal to choose destination tables.
146
136
147
137
:::image type="content" source="media/monitor-event-hubs-reference/destination-table-toggle.png" alt-text="Screenshot of dialog box to set destination table." lightbox="media/monitor-event-hubs-reference/destination-table-toggle.png":::
148
138
@@ -155,7 +145,8 @@ You can view our sample queries to get started with different log categories.
Runtime audit logs capture aggregated diagnostic information for all data plane access operations (such as send or receive events) in Event Hubs.
160
151
161
152
> [!NOTE]
@@ -225,7 +216,7 @@ Resource specific table entry:
225
216
226
217
```
227
218
228
-
## Application metrics logs
219
+
###Application metrics logs
229
220
230
221
Application metrics logs capture the aggregated information on certain metrics related to data plane operations. The captured information includes the following runtime metrics.
231
222
@@ -245,7 +236,7 @@ Application metrics logs capture the aggregated information on certain metrics r
245
236
|`OffsetCommit`| Number of offset commit calls made to the event hub |
246
237
|`OffsetFetch`| Number of offset fetch calls made to the event hub. |
247
238
248
-
## Diagnostic Error Logs
239
+
###Diagnostic Error Logs
249
240
250
241
Diagnostic error logs capture error messages for any client side, throttling, and Quota exceeded errors. They provide detailed diagnostics for error identification.
251
242
@@ -306,22 +297,6 @@ Resource specific table entry:
0 commit comments