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
Copy file name to clipboardExpand all lines: articles/azure-monitor/essentials/metrics-charts.md
+9-11Lines changed: 9 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -132,7 +132,7 @@ For a deeper discussion of how metric aggregation works, see [Azure Monitor metr
132
132
133
133
## Filters
134
134
135
-
You can apply filters to charts whose metrics have dimensions. For example, imagine a *Transaction count* metric that has a *Response type* dimension. This dimension indicates whether the response from transactions succeeded or failed. If you filter on this dimension, you'll see a chart line for only successful or only failed transactions.
135
+
You can apply filters to charts whose metrics have dimensions. For example, imagine a *Transaction count* metric that has a *Response type* dimension. This dimension indicates whether the response from transactions succeeded or failed. If you filter on this dimension, a chart line is displayed for only successful or only failed transactions.
136
136
137
137
### Add a filter
138
138
@@ -177,7 +177,7 @@ You can split a metric by dimension to visualize how different segments of the m
177
177
:::image type="content" source="./media/metrics-charts/segment-dimension-sort.png" alt-text="Screenshot that shows sort order on split values." lightbox="./media/metrics-charts/segment-dimension-sort.png":::
178
178
179
179
1. Segment by multiple segments by selecting multiple dimensions from the values dropdown. The legends shows a comma-separated list of dimension values for each segment
180
-
:::image type="content" source="./media/metrics-charts/segment-dimension-multiple.png" alt-text="Screenshot that shows multiple segments selected, and the corresponding chart below." lightbox="./media/metrics-charts/segment-dimension-multiple.png":::
180
+
:::image type="content" source="./media/metrics-charts/segment-dimension-multiple.png" alt-text="Screenshot that shows multiple segments selected, and the corresponding chart." lightbox="./media/metrics-charts/segment-dimension-multiple.png":::
181
181
182
182
1. Click away from the grouping selector to close it.
183
183
@@ -232,7 +232,7 @@ To create an alert rule,
232
232
233
233
:::image source="./media/metrics-charts/new-alert.png" alt-text="Screenshot that shows the New alert rule button." lightbox="./media/metrics-charts/new-alert.png":::
234
234
235
-
1. On the **Condition** the **Signal name** is defaulted to the metric from your chart. You can choose a different metric.
235
+
1. On the **Condition**tab, the **Signal name** is defaulted to the metric from your chart. You can choose a different metric.
236
236
237
237
1. Enter a **Threshold value**. The threshold value is the value that triggers the alert. The Preview chart shows the threshold value as a horizontal line over the metric values.
238
238
@@ -251,26 +251,24 @@ For more information, see [Create, view, and manage metric alerts](../alerts/ale
251
251
252
252
## Correlate metrics to logs
253
253
254
-
To help customers diagnose the root cause of anomalies in their metrics chart, we created the *Drill into Logs* feature. Drill into Logs allows customers to correlate spikes in their metrics chart to logs and queries.
254
+
**Drill into Logs** helps you diagnose the root cause of anomalies in your metrics chart. Drilling into logs allows you to correlate spikes in your metrics chart to logs and queries.
255
255
256
-
This table summarizes the types of logs and queries provided:
256
+
The following table summarizes the types of logs and queries provided:
257
257
258
258
| Term | Definition |
259
259
|------------------|-------------|
260
260
| Activity logs | Provides insight into the operations on each Azure resource in the subscription from the outside (the management plane) in addition to updates on Service Health events. Use the Activity log to determine the what, who, and when for any write operations (PUT, POST, DELETE) taken on the resources in your subscription. There's a single Activity log for each Azure subscription. |
261
-
| Diagnostic log | Provides insight into operations that were performed within an Azure resource (the data plane), for example getting a secret from a Key Vault or making a request to a database. The content of resource logs varies by the Azure service and resource type. **Note:** Must be provided by service and enabled by customer. |
262
-
| Recommended log | Scenario-based queries that customer can use to investigate anomalies in their Metrics Explorer. |
261
+
| Diagnostic log | Provides insight into operations that were performed within an Azure resource (the data plane). For example, getting a secret from a Key Vault or making a request to a database. The content of resource logs varies by the Azure service and resource type. You must enable logs for the resource. |
262
+
| Recommended log | Scenario-based queries that you can use to investigate anomalies in Metrics Explorer. |
263
263
264
-
Currently, Drill into Logs is available for select resource providers. The resource providers that have the complete Drill into Logs experience are:
264
+
Currently, Drill into Logs is available for select resource providers. The following resource providers offer the complete Drill into Logs experience:
265
265
266
266
- Application Insights
267
267
- Autoscale
268
268
- App Services
269
269
- Storage
270
270
271
-
This screenshot shows a sample for the Application Insights resource provider.
272
-
273
-

271
+
:::image source="./media/metrics-charts/drill-into-log-ai.png" alt-text="Screenshot that shows a spike in failures in app insights metrics pane." lightbox="./media/metrics-charts/drill-into-log-ai.png":::
274
272
275
273
1. To diagnose the spike in failed requests, select **Drill into Logs**.
0 commit comments