Skip to content

Commit 61ca311

Browse files
authored
updated alt-txt
1 parent 8d432c0 commit 61ca311

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -147,10 +147,10 @@ Using *Runtime audit logs* you can capture aggregated diagnostic information for
147147
### 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
@@ -168,7 +168,7 @@ 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

@@ -181,8 +181,9 @@ 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/./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)