Skip to content

Commit c5b62aa

Browse files
committed
MIssing link to data sources article
1 parent 0bd17a1 commit c5b62aa

File tree

2 files changed

+88
-0
lines changed

2 files changed

+88
-0
lines changed
Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
title: Monitor the health of your Azure Monitor Log Search alerts
3+
description: This article how to monitor the health of an Azure Monitor Log Search alerts.
4+
ms.topic: how-to
5+
author: AbbyMSFT
6+
ms.author: abbyweisberg
7+
ms.reviewer: nolavime
8+
ms.date: 02/07/2024
9+
10+
#Customer-intent: As an Azure Monitor administrator, I want to know when there are latency issues with an Azure Monitor log search alert, so I can act to resolve the issue, contact Microsoft for support, or track that is Azure is meeting its SLA.
11+
---
12+
13+
# Monitor the health of your Azure Monitor Log search alerts
14+
15+
[Azure Service Health](../../service-health/overview.md) monitors the health of your cloud resources, including your Azure Monitor log search alerts. When a log search alert is healthy, data you collect using your query is available for analysis in a relatively short period of time, known as [latency](../logs/data-ingestion-time.md). This article explains how to view the health status of your log search alerts.
16+
17+
Azure Service Health monitors:
18+
19+
- [Resource health](../../service-health/resource-health-overview.md): information about the health of your individual cloud resources, such as a specific Log Analytics workspace.
20+
- [Service health](../../service-health/service-health-overview.md): information about the health of the Azure services and regions you're using, which might affect your Log Analytics workspace, including communications about outages, planned maintenance activities, and other health advisories.
21+
22+
## Permissions required
23+
24+
- To view Log Analytics workspace health, you need `*/read` permissions to the Log Analytics workspace, as provided by the [Log Analytics Reader built-in role](./manage-access.md#log-analytics-reader), for example.
25+
- To set up health status alerts, you need `Microsoft.Insights/ActivityLogAlerts/Write` permissions to the Log Analytics workspace, as provided by the [Monitoring Contributor built-in role](../roles-permissions-security.md#monitoring-contributor), for example.
26+
27+
## View Log Analytics workspace health and set up health status alerts
28+
29+
30+
To view your Log Analytics workspace health and set up health status alerts:
31+
32+
1. Select **Resource health** from the Log Analytics workspace menu.
33+
34+
The **Resource health** screen shows:
35+
36+
- **Health history**: Indicates whether Azure Service Health has detected latency or query execution issues in the specific Log Analytics workspace. To further investigate latency issues related to your workspace, see [Investigate latency](#investigate-log-analytics-workspace-health-issues).
37+
- **Azure service issues**: Displayed when a known issue with an Azure service might affect latency in the Log Analytics workspace. Select the message to view details about the service issue in Azure Service Health.
38+
39+
> [!NOTE]
40+
> - Service health notifications do not indicate that your Log Analytics workspace is necessarily affected by the know service issue. If your Log Analytics workspace resource health status is **Available**, Azure Service Health did not detect issues in your workspace.
41+
> - Resource Health excludes data types for which long ingestion latency is expected. For example, Application Insights data types that calculate the application map data and are known to add latency.
42+
43+
44+
:::image type="content" source="media/data-ingestion-time/log-analytics-workspace-latency.png" lightbox="media/data-ingestion-time/log-analytics-workspace-latency.png" alt-text="Screenshot that shows the Resource health screen for a Log Analytics workspace.":::
45+
46+
This table describes the possible resource health status values for a Log Analytics workspace:
47+
48+
| Resource health status | Description |
49+
|-|-|
50+
|Available| [Average latency](../logs/data-ingestion-time.md#average-latency) and no query execution issues detected.|
51+
|Unavailable|Higher than average latency detected.|
52+
|Degraded|Query failures detected.|
53+
|Unknown|Currently unable to determine Log Analytics workspace health because you haven't run queries or ingested data to this workspace recently.|
54+
55+
1. To set up health status alerts, you can either [enable recommended out-of-the-box alert](../alerts/alerts-overview.md#recommended-alert-rules) rules, or manually create new alert rules.
56+
- To create a new alert rule:
57+
1. Select **Add resource health alert**.
58+
59+
The **Create alert rule** wizard opens, with the **Scope** and **Condition** panes prepopulated. By default, the rule triggers alerts all status changes in all Log Analytics workspaces in the subscription. If necessary, you can edit and modify the scope and condition at this stage.
60+
61+
:::image type="content" source="media/data-ingestion-time/log-analytics-workspace-latency-alert-rule.png" lightbox="media/data-ingestion-time/log-analytics-workspace-latency-alert-rule.png" alt-text="Screenshot that shows the Create alert rule wizard for Log Analytics workspace latency issues.":::
62+
63+
1. Follow the rest of the steps in [Create a new alert rule in the Azure portal](../alerts/alerts-create-new-alert-rule.md#create-or-edit-an-alert-rule-in-the-azure-portal).
64+
65+
## View Log Analytics workspace health metrics
66+
67+
Azure Monitor exposes a set of metrics that provide insight into Log Analytics workspace health.
68+
69+
To view Log Analytics workspace health metrics:
70+
71+
1. Select **Metrics** from the Log Analytics workspace menu. This opens [Metrics Explorer](../essentials/metrics-charts.md) in context of your Log Analytics workspace.
72+
1. In the **Metric** field, select one of the Log Analytics workspace health metrics:
73+
74+
| Metric name | Description |
75+
| - | - |
76+
| Query count | Total number of user queries in the Log Analytics workspace within the selected time range.<br>This number includes only user-initiated queries, and doesn't include queries initiated by Sentinel rules and alert-related queries. |
77+
| Query failure count | Total number of failed user queries in the Log Analytics workspace within the selected time range.<br>This number includes all queries that return 5XX response codes - except 504 *Gateway Timeout* - which indicate an error related to the application gateway or the backend server.|
78+
| AvailabilityRate_Query | Percentage of successful user queries in the Log Analytics workspace within the selected time range.<br>This number includes all queries that return 2XX, 4XX, and 504 response codes; in other words, all user queries that don't result in a service error. |
79+
80+
81+
## Next steps
82+
83+
Learn more about:
84+
85+
- [Log Analytics Workspace Insights](../logs/log-analytics-workspace-insights-overview.md).
86+
- [Querying log data in Azure Monitor Logs](../logs/get-started-queries.md).
87+

articles/azure-monitor/toc.yml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1076,6 +1076,7 @@ items:
10761076
- name: Azure Workbook components
10771077
items:
10781078
- name: Data sources
1079+
href: visualize/workbooks-data-sources.md
10791080
- name: Visualizations
10801081
items:
10811082
- name: Overview

0 commit comments

Comments
 (0)