diff --git a/articles/azure-monitor/essentials/data-collection-metrics.md b/articles/azure-monitor/essentials/data-collection-metrics.md index 99fc13fcf7..c9d1f15dc4 100644 --- a/articles/azure-monitor/essentials/data-collection-metrics.md +++ b/articles/azure-monitor/essentials/data-collection-metrics.md @@ -100,7 +100,7 @@ Data collection rules are defined in a JSON object. The following properties are |Property|Description| |---|---| -|`dataSources.platformTelemetry.streams`| Lists the resource types to collect metrics from in the format: `:Metrics-Group-All |`
For example, `Microsoft.Compute/virtualMachines:Percentage CPU`| +|`dataSources.platformTelemetry.streams`| Lists the resource types and the metrics. Specify `Metrics-Group-All` to collect all metrics for the resource or specify individual metrics. Format: `:Metrics-Group-All | `
For example, `Microsoft.Compute/virtualMachines:Percentage CPU`| |`dataSources.platformTelemetry.name`| The name of the data source.| |`destinations`| The destination for the metrics. Only one destination is supported per DCR.
Valid Destinations types:
`storageAccounts`
`logAnalytics`
`eventHubs` | |`dataflows.streams`| A list of streams to pass to the destination in the format: `:Metrics-Group-All |`
For example, Microsoft.Compute/virtualMachines:Percentage CPU"| @@ -206,6 +206,8 @@ To use a user assigned identity, add the `identity` object as follows: When specifying the metrics to export, you can filter the metrics by name or request all metrics by using `Metrics-Group-All`. For a list of supported metrics, see [Supported metrics and log categories by resource type](/azure/azure-monitor/reference/supported-metrics/metrics-index#supported-metrics-and-log-categories-by-resource-type). +To specify more than one metric from the same resource type, create a separate stream item for each metric. + The following example shows how to filter metrics by name. ```JSON @@ -216,6 +218,8 @@ The following example shows how to filter metrics by name. { "streams": [ "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows", "Microsoft.Compute/virtualMachineScaleSets:Percentage CPU", "Microsoft.Cache/redis:Cache Hits" ], @@ -235,6 +239,8 @@ The following example shows how to filter metrics by name. { "streams": [ "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows", "Microsoft.Compute/virtualMachineScaleSets:Percentage CPU", "Microsoft.Cache/redis:Cache Hits" ], @@ -253,6 +259,8 @@ The following example shows how to filter metrics by name. The following examples show sample DCR JSON objects for metrics export to each destination type. +### [Log Analytics workspaces](#tab/log-analytics-workspaces) + ### Log Analytics workspaces The following example shows a data collection rule for metrics that sends specific metrics from virtual machines, virtual machine scale sets, and all key vault metrics to a Log Analytics workspace: @@ -265,6 +273,8 @@ The following example shows a data collection rule for metrics that sends specif { "streams": [ "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows", "Microsoft.Compute/virtualMachineScaleSets:Available Memory Bytes", "Microsoft.KeyVault/vaults:Metrics-Group-All" ], @@ -284,6 +294,8 @@ The following example shows a data collection rule for metrics that sends specif { "streams": [ "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows", "Microsoft.Compute/virtualMachineScaleSets:Available Memory Bytes", "Microsoft.KeyVault/vaults:Metrics-Group-All" ], @@ -299,10 +311,11 @@ The following example shows a data collection rule for metrics that sends specif "location": "centralus" } ``` +### [Storage accounts](#tab/storage-accounts) ### Storage accounts -The following example shows a data collection rule for metrics that sends all metrics from virtual machines, virtual machine scale sets, Redis cache, and Key Vaults to a storage account. +The following example shows a data collection rule for metrics that sends`Percentage CPU`, `Disk Read Bytes`, and `Inbound Flows` metrics from virtual machines, and all metrics for virtual machine scale sets, Redis cache, and Key Vaults to a storage account. ```json { @@ -311,7 +324,9 @@ The following example shows a data collection rule for metrics that sends all me "platformTelemetry": [ { "streams": [ - "Microsoft.Compute/virtualMachines:Metrics-Group-All", + "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows" "Microsoft.Compute/virtualMachineScaleSets:Metrics-Group-All", "Microsoft.Cache/redis:Metrics-Group-All", "Microsoft.keyvault/vaults:Metrics-Group-All" @@ -332,7 +347,9 @@ The following example shows a data collection rule for metrics that sends all me "dataFlows": [ { "streams": [ - "Microsoft.Compute/virtualMachines:Metrics-Group-All", + "Microsoft.Compute/virtualMachines:Percentage CPU", + "Microsoft.Compute/virtualMachines:Disk Read Bytes", + "Microsoft.Compute/virtualMachines:Inbound Flows" "Microsoft.Compute/virtualMachineScaleSets:Metrics-Group-All", "Microsoft.Cache/redis:Metrics-Group-All", "Microsoft.keyvault/vaults:Metrics-Group-All" @@ -351,10 +368,11 @@ The following example shows a data collection rule for metrics that sends all me } ``` +### [Event Hubs](#tab/event-hubs) ### Event Hubs -The following example shows a data collection rule for metrics export that sends all metrics from virtual machines, and the `ServiceApiHit` metric from Key Vaults to Event Hubs. +The following example shows a data collection rule for metrics export that sends all metrics from virtual machines, and the `ServiceApiHit` and `Availability` metrics from Key Vaults to Event Hubs. ```json { @@ -364,7 +382,9 @@ The following example shows a data collection rule for metrics export that sends { "streams": [ "Microsoft.Compute/virtualMachines:Metrics-Group-All", - "Microsoft.keyvault/vaults:ServiceApiHit" + "Microsoft.keyvault/vaults:ServiceApiHit", + "Microsoft.keyvault/vaults:Availability" + ], "name": "myPlatformTelemetryDataSource" } @@ -382,7 +402,8 @@ The following example shows a data collection rule for metrics export that sends { "streams": [ "Microsoft.Compute/virtualMachines:Metrics-Group-All", - "Microsoft.keyvault/vaults:ServiceApiHit" + "Microsoft.keyvault/vaults:ServiceApiHit", + "Microsoft.keyvault/vaults:Availability" ], "destinations": [ "hub1" @@ -398,6 +419,7 @@ The following example shows a data collection rule for metrics export that sends } ``` +--- ## Create DCRs for metrics export diff --git a/articles/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy.md b/articles/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy.md index 9de898e6e1..6b31d0d147 100644 --- a/articles/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy.md +++ b/articles/azure-monitor/essentials/migrate-to-azure-storage-lifecycle-policy.md @@ -29,6 +29,45 @@ An existing diagnostic setting logging to a storage account. ## Migration procedures +Use the following CLI command to check if a resource has a diagnostic setting: + +```azurecli + az monitor diagnostic-settings list --resource +``` +The output shows whether the diagnostic setting sends the data to a storage account, for example: + +```JSON +[ + { + "id": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourcegroups/rg-001/providers/microsoft.insights/datacollectionrules/dcr-east2/providers/microsoft.insights/diagnosticSettings/dsetting-1", + "logs": [ + { + "categoryGroup": "allLogs", + "enabled": true, + "retentionPolicy": { + "days": 0, + "enabled": false + } + } + ], + "metrics": [ + { + "category": "AllMetrics", + "enabled": false, + "retentionPolicy": { + "days": 0, + "enabled": false + } + } + ], + "name": "dsetting-1", + "resourceGroup": "rg-001", + "storageAccountId": "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e/resourceGroups/rg-DCR/providers/Microsoft.Storage/storageAccounts/logs001", + "type": "Microsoft.Insights/diagnosticSettings" + } +] +``` + ## [Azure portal](#tab/portal) To migrate your diagnostics settings retention rules, follow the steps below: diff --git a/articles/azure-monitor/essentials/prometheus-workbooks.md b/articles/azure-monitor/essentials/prometheus-workbooks.md index 5a9affc358..153ee6c2bf 100644 --- a/articles/azure-monitor/essentials/prometheus-workbooks.md +++ b/articles/azure-monitor/essentials/prometheus-workbooks.md @@ -3,7 +3,7 @@ title: Query Prometheus metrics using Azure workbooks description: Query Prometheus metrics in the portal using Azure Workbooks. author: EdB-MSFT ms.topic: conceptual -ms.date: 07/17/2023 +ms.date: 09/23/2024 ms.author: edbaynash --- @@ -12,10 +12,14 @@ ms.author: edbaynash Create dashboards powered by Azure Monitor managed service for Prometheus using [Azure Workbooks](../visualize/workbooks-overview.md). This article introduces workbooks for Azure Monitor workspaces and shows you how to query Prometheus metrics using Azure workbooks and the Prometheus query language (PromQL). +You can also query Prometheus metrics using PromQL from the metrics explorer in an Azure Monitor workspace. For more information, see [Azure Monitor metrics explorer with PromQL (Preview)](./metrics-explorer.md). + + ## Prerequisites + To query Prometheus metrics from an Azure Monitor workspace, you need the following: - An Azure Monitor workspace. To create an Azure Monitor workspace, see [Create an Azure Monitor Workspace](./azure-monitor-workspace-overview.md?tabs=azure-portal.md). -- Your Azure Monitor workspace must be [collecting Prometheus metrics](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana) from an AKS cluster. +- Your Azure Monitor workspace must be [collecting Prometheus metrics](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana) from an AKS cluster, or from a Virtual Machine or Virtual Machine Scale Set. For more information, see [Send Prometheus metrics from virtual machines, scale sets, or Kubernetes clusters to an Azure Monitor workspace](./prometheus-remote-write-virtual-machines.md). - The user must be assigned role that can perform the **microsoft.monitor/accounts/read** operation on the Azure Monitor workspace. ## Prometheus Explorer workbook @@ -58,11 +62,11 @@ Workbooks support many visualizations and Azure integrations. For more informati ## Troubleshooting -If you receive a message indicating that "You currently do not have any Prometheus data ingested to this Azure Monitor workspace": +If you receive a message stating that "You currently do not have any Prometheus data ingested to this Azure Monitor workspace": - Verify that you have turned on metrics collection in the Monitored clusters blade of your Azure Monitor workspace. -If your workbook query does not return data with a message "You do not have query access": +If your workbook query doesn't return data and returns with the message "You do not have query access": - Check that you have sufficient permissions to perform **microsoft.monitor/accounts/read** assigned through Access Control (IAM) in your Azure Monitor workspace. - Confirm if your Networking settings support query access. You might need to enable private access through your private endpoint or change settings to allow public access. @@ -81,5 +85,7 @@ This section provides answers to common questions. ## Next steps * [Collect Prometheus metrics from AKS cluster](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana) +* [Send Prometheus metrics from virtual machines, scale sets, or Kubernetes clusters to an Azure Monitor workspace](./prometheus-remote-write-virtual-machines.md) +* [Azure Monitor metrics explorer with PromQL (Preview)](./metrics-explorer.md) * [Azure Monitor workspace](./azure-monitor-workspace-overview.md) * [Use Azure Monitor managed service for Prometheus as data source for Grafana using managed system identity](./prometheus-grafana.md) diff --git a/articles/azure-monitor/logs/availability-zones.md b/articles/azure-monitor/logs/availability-zones.md index b3880b5936..53b8690379 100644 --- a/articles/azure-monitor/logs/availability-zones.md +++ b/articles/azure-monitor/logs/availability-zones.md @@ -47,7 +47,6 @@ A subset of the availability zones that support data resilience currently also s | East US | | :white_check_mark: | | | East US 2 | | :white_check_mark: | :white_check_mark: | | South Central US | :white_check_mark: | :white_check_mark: | | -| Spain Central | :white_check_mark: | :white_check_mark: | :white_check_mark: | | West US 2 | | :white_check_mark: | :white_check_mark: | | West US 3 | :white_check_mark: | :white_check_mark: | | | **Asia Pacific** | | | | @@ -64,6 +63,7 @@ A subset of the availability zones that support data resilience currently also s | North Europe | :white_check_mark: | :white_check_mark: | :white_check_mark: | | Norway East | :white_check_mark: | :white_check_mark: | | | Poland Central | | :white_check_mark: | | +| Spain Central | :white_check_mark: | :white_check_mark: | :white_check_mark: | | Sweden Central | :white_check_mark: | :white_check_mark: | | | Switzerland North | | :white_check_mark: | | | UK South | :white_check_mark: | :white_check_mark: | | diff --git a/articles/azure-monitor/visualize/workbooks-overview.md b/articles/azure-monitor/visualize/workbooks-overview.md index 88c570deea..711eb6288b 100644 --- a/articles/azure-monitor/visualize/workbooks-overview.md +++ b/articles/azure-monitor/visualize/workbooks-overview.md @@ -5,7 +5,7 @@ services: azure-monitor author: AbbyMSFT ms.author: abbyweisberg ms.topic: conceptual -ms.date: 09/17/2024 +ms.date: 09/23/2024 ms.reviewer: gardnerjr --- diff --git a/articles/service-health/alerts-activity-log-service-notifications-portal.md b/articles/service-health/alerts-activity-log-service-notifications-portal.md index 200ed8ef14..8fe1c026f3 100644 --- a/articles/service-health/alerts-activity-log-service-notifications-portal.md +++ b/articles/service-health/alerts-activity-log-service-notifications-portal.md @@ -1,13 +1,13 @@ --- -title: Receive activity log alerts on Azure service notifications using Azure portal -description: Learn how to use the Azure portal to set up activity log alerts for service health notifications by using the Azure portal. +title: Receive Service health alerts on Azure service notifications using Azure portal +description: Learn how to use the Azure portal to set up Service health alerts for service health notifications by using the Azure portal. ms.topic: quickstart ms.date: 07/31/2024 --- -# Create activity log alerts on service notifications using the Azure portal +# Create Service health alerts on service notifications using the Azure portal -This article shows you how to use the Azure portal to set up activity log alerts for service health notifications by using the Azure portal. +This article shows you how to use the Azure portal to set up Service health alerts for service health notifications by using the Azure portal. Service health notifications are stored in the [Azure activity log](../azure-monitor/essentials/platform-logs-overview.md). Given the large volume of information stored in the activity log, there is a separate user interface to make it easier to view and set up alerts on service health notifications.