Skip to content

Commit de214d4

Browse files
Additional edits.
1 parent 00fb7a8 commit de214d4

File tree

2 files changed

+11
-11
lines changed

2 files changed

+11
-11
lines changed

articles/event-hubs/monitor-event-hubs-reference.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Monitoring data reference for Azure Event Hubs
3-
description: This article contains important reference material you need when you monitor Azure Event Hubs.
4-
ms.date: 06/19/2024
3+
description: This article contains important reference material you need when you monitor Azure Event Hubs by using Azure Monitor.
4+
ms.date: 06/20/2024
55
ms.custom: horz-monitor, subject-monitoring
66
ms.topic: reference
77
ms.service: azure-event-hubs
@@ -33,9 +33,9 @@ The following table lists the metrics available for the Microsoft.EventHub/Names
3333
[!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
3434
[!INCLUDE [<ResourceType/namespace>](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-eventhub-namespaces-metrics-include.md)]
3535

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`.
36+
The following tables list 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`.
3737

38-
Request metrics count the number of data and management operations requests. This table provides more information about values from the preceding tables.
38+
*Request metrics* count the number of data and management operations requests. This table provides more information about values from the preceding tables.
3939

4040
| Metric name | Description |
4141
|:--------------------|:------------|
@@ -55,8 +55,8 @@ This table provides more information for message metrics from the preceding tabl
5555
| Size | Size of an event hub in bytes. |
5656

5757
> [!NOTE]
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.
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.
58+
> - These values are point-in-time values. Incoming messages that are consumed immediately after that point-in-time might not be reflected in these metrics.
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.
6060
6161
This table provides more information for capture metrics from the preceding tables.
6262

@@ -82,21 +82,21 @@ This table provides more information for error metrics from the preceding tables
8282
| User Errors | The number of requests not processed because of user errors over a specified period. |
8383
| Quota Exceeded Errors | The number of errors caused by exceeding quotas over a specified period. |
8484

85-
The following two types of errors are classified as **user errors**:
85+
The following two types of errors are classified as *user errors*:
8686

8787
1. Client-side errors (In HTTP that would be 400 errors).
8888
2. Errors that occur while processing messages.
8989

9090
> [!NOTE]
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.
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 can collect failures from Event Hubs clients so that you can view them in user logs.
9292
9393
[!INCLUDE [horz-monitor-ref-metrics-dimensions-intro](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions-intro.md)]
9494

9595
[!INCLUDE [horz-monitor-ref-metrics-dimensions](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-dimensions.md)]
9696

9797
| Dimension name | Description |
9898
|:----------------|:------------|
99-
| 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. |
99+
| 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. |
100100
| OperationResult | |
101101
| Replica | |
102102
| Role | |

articles/event-hubs/monitor-event-hubs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Monitor Azure Event Hubs
33
description: Learn how to use Azure Monitor to view, analyze, and create alerts on metrics from Azure Event Hubs.
4-
ms.date: 06/19/2024
4+
ms.date: 06/20/2024
55
ms.custom: horz-monitor, subject-monitoring
66
ms.topic: conceptual
77
ms.service: azure-event-hubs
@@ -79,7 +79,7 @@ For the available resource log categories, their associated Log Analytics tables
7979

8080
### Analyze logs
8181

82-
Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable __Send information to Log Analytics__. For more information, see the [Metrics](#azure-monitor-platform-metrics) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs has the capability to dispatch logs to either of two destination tables: Azure Diagnostic or Resource specific tables in Log Analytics. For a detailed reference of the logs and metrics, see [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md).
82+
Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable **Send information to Log Analytics**. For more information, see the [Metrics](#azure-monitor-platform-metrics) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs has the capability to dispatch logs to either of two destination tables: Azure Diagnostic or Resource specific tables in Log Analytics. For a detailed reference of the logs and metrics, see [Azure Event Hubs monitoring data reference](monitor-event-hubs-reference.md).
8383

8484
> [!IMPORTANT]
8585
> When you select **Logs** from the Azure Event Hubs menu, Log Analytics is opened with the query scope set to the current workspace. This means that log queries will only include data from that resource. If you want to run a query that includes data from other databases or data from other Azure services, select **Logs** from the **Azure Monitor** menu. See [Log query scope and time range in Azure Monitor Log Analytics](../azure-monitor/logs/scope.md) for details.

0 commit comments

Comments
 (0)