From 570eb884b8725d4661e5ec362cdb7b913b3ad5d8 Mon Sep 17 00:00:00 2001 From: "r.rana1" Date: Tue, 11 Nov 2025 15:20:28 +0530 Subject: [PATCH 1/3] NLB-7129: update metrics migration steps --- .../nginxaas-azure/monitoring/migrate-to-platform-metrics.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md index 70de8a906..e1a6a2a2f 100644 --- a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md +++ b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md @@ -19,11 +19,6 @@ Follow the steps in this section to migrate your deployment monitoring from Cust 2. If the pre-requisites are met, Platform metrics are enabled by default on all NGINXaaS deployment. Verify that you are able to see the new metrics in Azure Monitor under the `Standard Metrics` namespace. 3. Turn off legacy monitoring: - - Using the Azure portal - 1. In the Azure portal, go to the **NGINX monitoring** page for your NGINXaaS deployment. - 2. Turn off the **Send metrics to Azure Monitor** setting. - 3. Select **Save**. - - Using Terraform 1. Set `diagnose_support_enabled` to false in the `azurerm_nginx_deployment` resource. 2. Run `terraform plan` followed by `terraform apply` to upgrade the deployment. From ad606505a6fe21dbe174c830f68579f02e6e4f7c Mon Sep 17 00:00:00 2001 From: "r.rana1" Date: Fri, 14 Nov 2025 11:34:53 +0530 Subject: [PATCH 2/3] migration steps for transitioning to platform metrics --- .../monitoring/migrate-to-platform-metrics.md | 29 +++++++++++-------- 1 file changed, 17 insertions(+), 12 deletions(-) diff --git a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md index e1a6a2a2f..6b78499b3 100644 --- a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md +++ b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md @@ -17,15 +17,20 @@ Follow the steps in this section to migrate your deployment monitoring from Cust 1. Verify that your NGINXaaS deployment meets the [pre-requisites]({{< ref "/nginxaas-azure/monitoring/enable-monitoring.md#prerequisites">}}) for Platform metrics to work. 2. If the pre-requisites are met, Platform metrics are enabled by default on all NGINXaaS deployment. Verify that you are able to see the new metrics in Azure Monitor under the `Standard Metrics` namespace. -3. Turn off legacy monitoring: - - - Using Terraform - 1. Set `diagnose_support_enabled` to false in the `azurerm_nginx_deployment` resource. - 2. Run `terraform plan` followed by `terraform apply` to upgrade the deployment. - - - Using the Azure CLI - Run the following command: - ```shell - az nginx deployment update --name myDeployment --resource-group \ - myResourceGroup --enable-diagnostics="false" - ``` +3. **Migrate existing alert rules** to use Platform metrics instead of Custom metrics: + + If you have existing alert rules configured for Custom metrics, you need to update them to use the equivalent Platform metrics signals. + + 1. In the [Azure portal](https://portal.azure.com), go to **Monitor** > **Alerts**. + 2. Select **Alert rules**. + 3. Select the alert rule you want to migrate, then select **Edit**. + 4. In the **Conditions** tab, select the current **Signal name** to modify it. + 5. Replace the Custom metrics signal with the corresponding Platform metrics signal: + - Custom metrics signals use the `Azure.ApplicationInsights` namespace + - Platform metrics signals use the `Standard Metrics` namespace + 6. Update the signal name to point to the equivalent Platform metric. For example: + - Replace `nginx.http.request.count` (Custom metric) with `nginx.http.request.count` (Platform metric) + 7. Review and adjust the alert logic, thresholds, and conditions as needed. + 8. Select **Review + create**, then **Create** to save the updated alert rule. + + {{< call-out "note" >}}For a complete list of available Platform metrics, see the [metrics catalog]({{< ref "/nginxaas-azure/monitoring/metrics-catalog.md" >}}). To learn more about editing alert rules, refer to the [Edit an existing alert rule](https://learn.microsoft.com/en-us/azure/azure-monitor/alerts/alerts-create-metric-alert-rule#edit-an-existing-alert-rule) section in the Azure documentation.{{< /call-out >}} From 745a36dbadc82918a2927dcd986c97da598488b7 Mon Sep 17 00:00:00 2001 From: "r.rana1" Date: Fri, 14 Nov 2025 22:41:56 +0530 Subject: [PATCH 3/3] update migration and clarify signal name usage --- .../monitoring/migrate-to-platform-metrics.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md index 6b78499b3..f5155318c 100644 --- a/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md +++ b/content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md @@ -26,10 +26,8 @@ Follow the steps in this section to migrate your deployment monitoring from Cust 3. Select the alert rule you want to migrate, then select **Edit**. 4. In the **Conditions** tab, select the current **Signal name** to modify it. 5. Replace the Custom metrics signal with the corresponding Platform metrics signal: - - Custom metrics signals use the `Azure.ApplicationInsights` namespace - - Platform metrics signals use the `Standard Metrics` namespace - 6. Update the signal name to point to the equivalent Platform metric. For example: - - Replace `nginx.http.request.count` (Custom metric) with `nginx.http.request.count` (Platform metric) + - Platform metrics signals use the `NGINXaaS Standard Metrics` namespace + 6. The metric name remains the same between Custom and Platform metrics (for example, `nginx.http.request.count`). No update to the signal name is needed. 7. Review and adjust the alert logic, thresholds, and conditions as needed. 8. Select **Review + create**, then **Create** to save the updated alert rule.