Skip to content

Commit 6e54009

Browse files
committed
2 parents 43a93f9 + 55a1439 commit 6e54009

File tree

1 file changed

+14
-13
lines changed

1 file changed

+14
-13
lines changed

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

Lines changed: 14 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Monitoring Azure Event Hubs
33
description: Learn how to use Azure Monitor to view, analyze, and create alerts on metrics from Azure Event Hubs.
44
ms.topic: conceptual
55
ms.custom: subject-monitoring
6-
ms.date: 02/10/2022
6+
ms.date: 06/16/2022
77
---
88

99
# Monitor Azure Event Hubs
@@ -58,7 +58,7 @@ If you use **Log Analytics** to store the diagnostic logging information, the in
5858
5959
The metrics and logs you can collect are discussed in the following sections.
6060

61-
## Analyzing metrics
61+
## Analyze metrics
6262
You can analyze metrics for Azure Event Hubs, along with metrics from other Azure services, by selecting **Metrics** from the **Azure Monitor** section on the home page for your Event Hubs namespace. See [Getting started with Azure Metrics Explorer](../azure-monitor/essentials/metrics-getting-started.md) for details on using this tool. For a list of the platform metrics collected, see [Monitoring Azure Event Hubs data reference metrics](monitor-event-hubs-reference.md#metrics).
6363

6464
![Metrics Explorer with Event Hubs namespace selected](./media/monitor-event-hubs/metrics.png)
@@ -68,12 +68,12 @@ For reference, you can see a list of [all resource metrics supported in Azure Mo
6868
> [!TIP]
6969
> Azure Monitor metrics data is available for 90 days. However, when creating charts only 30 days can be visualized. For example, if you want to visualize a 90 day period, you must break it into three charts of 30 days within the 90 day period.
7070
71-
### Filtering and splitting
71+
### Filter and split
7272
For metrics that support dimensions, you can apply filters using a dimension value. For example, add a filter with `EntityName` set to the name of an event hub. You can also split a metric by dimension to visualize how different segments of the metric compare with each other. For more information of filtering and splitting, see [Advanced features of Azure Monitor](../azure-monitor/essentials/metrics-charts.md).
7373

7474
:::image type="content" source="./media/monitor-event-hubs/metrics-filter-split.png" alt-text="Image showing filtering and splitting metrics":::
7575

76-
## Analyzing logs
76+
## Analyze logs
7777
Using Azure Monitor Log Analytics requires you to create a diagnostic configuration and enable __Send information to Log Analytics__. For more information, see the [Collection and routing](#collection-and-routing) section. Data in Azure Monitor Logs is stored in tables, with each table having its own set of unique properties. Azure Event Hubs stores data in the following tables: **AzureDiagnostics** and **AzureMetrics**.
7878

7979
> [!IMPORTANT]
@@ -134,7 +134,7 @@ Following are sample queries that you can use to help you monitor your Azure Eve
134134
135135
```
136136
137-
## Using Runtime logs
137+
## Use runtime logs
138138
139139
Azure Event Hubs allows you to monitor and audit data plane interactions of your client applications using runtime audit logs and application metrics logs.
140140
@@ -144,21 +144,21 @@ Using *Runtime audit logs* you can capture aggregated diagnostic information for
144144
> [!NOTE]
145145
> Runtime audit logs are available only in **premium** and **dedicated** tiers.
146146
147-
### Enabling Runtime logs
147+
### Enable runtime logs
148148
You can enable either runtime audit logs or application metrics logs by selecting *Diagnostic settings* from the *Monitoring* section on the Event Hubs namespace page in Azure Portal. Click on *Add diagnostic setting* as shown below.
149149
150-
![Metrics Explorer with Event Hubs namespace selected](./media/monitor-event-hubs/add-diagnostic-settings.png)
150+
![Screenshot showing the Diagnostic settings page.](./media/monitor-event-hubs/add-diagnostic-settings.png)
151151
152152
Then you can enable log categories *RuntimeAuditLogs* or *ApplicationMetricsLogs* as needed.
153-
![Metrics Explorer with Event Hubs namespace selected](./media/monitor-event-hubs/configure-diagnostic-settings.png)
153+
![Screenshot showing the selection of RuntimeAuditLogs and ApplicationMetricsLogs.](./media/monitor-event-hubs/configure-diagnostic-settings.png)
154154
155155
Once runtime logs are enabled, Event Hubs will start collecting and storing them according to the diagnostic setting configuration.
156156
157-
### Publishing and consuming sample data
157+
### Publish and consume sample data
158158
To collect sample runtime audit logs in your Event Hubs namespace, you can publish and consume sample data using client applications which are based on [Event Hubs SDK](../event-hubs/event-hubs-dotnet-standard-getstarted-send.md) (AMQP) or using any [Apache Kafka client application](../event-hubs/event-hubs-quickstart-kafka-enabled-event-hubs.md).
159159
160160
161-
### Analyzing Runtime Audit logs
161+
### Analyze runtime audit logs
162162
You can analyze the collected runtime audit logs using the following sample query.
163163
164164
```kusto
@@ -168,21 +168,22 @@ AzureDiagnostics
168168
| where Category == "RuntimeAuditLogs"
169169
```
170170
Up on the execution of the query you should be able to obtain corresponding audit logs in the following format.
171-
![Metrics Explorer with Event Hubs namespace selected](./media/monitor-event-hubs/runtime-audit-logs.png)
171+
:::image type="content" source="./media/monitor-event-hubs/runtime-audit-logs.png" alt-text="Image showing the result of a sample query to analyze runtime audit logs." lightbox="./media/monitor-event-hubs/runtime-audit-logs.png":::
172172

173173
By analyzing these logs you should be able to audit how each client application interacts with Event Hubs. Each feild associated with runtime audit logs are defined in [runtime audit logs reference](../event-hubs/monitor-event-hubs-reference.md#runtime-audit-logs).
174174

175175

176-
### Analyzing Application metrics
176+
### Analyze application metrics
177177
You can analyze the collected application metrics logs using the following sample query.
178178

179179
```kusto
180180
AzureDiagnostics
181181
| where TimeGenerated > ago(1h)
182182
| where Category == "ApplicationMetricsLogs"
183183
```
184+
184185
Application metrics includes the following runtime metrics.
185-
![Metrics Explorer with Event Hubs namespace selected](./media/monitor-event-hubs/application-metrics-logs.png)
186+
:::image type="content" source="./media/monitor-event-hubs/application-metrics-logs.png" alt-text="Image showing the result of a sample query to analyze application metrics." lightbox="./media/monitor-event-hubs/application-metrics-logs.png":::
186187

187188
Therefore you can use application metrics to monitor runtime metrics such as consumer lag or active connection from a given client application. Each feild associated with runtime audit logs are defined in [applicaiton metrics logs reference](../event-hubs/monitor-event-hubs-reference.md#runtime-audit-logs).
188189

0 commit comments

Comments
 (0)