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
* NLB-7129: update metrics migration steps
* migration steps for transitioning to platform metrics
* update migration and clarify signal name usage
---------
Co-authored-by: Alan Dooley <a.dooley@f5.com>
Copy file name to clipboardExpand all lines: content/nginxaas-azure/monitoring/migrate-to-platform-metrics.md
+15-17Lines changed: 15 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,20 +17,18 @@ Follow the steps in this section to migrate your deployment monitoring from Cust
17
17
18
18
1. Verify that your NGINXaaS deployment meets the [pre-requisites]({{< ref "/nginxaas-azure/monitoring/enable-monitoring.md#prerequisites">}}) for Platform metrics to work.
19
19
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.
20
-
3. Turn off legacy monitoring:
21
-
22
-
- Using the Azure portal
23
-
1. In the Azure portal, go to the **NGINX monitoring** page for your NGINXaaS deployment.
24
-
2. Turn off the **Send metrics to Azure Monitor** setting.
25
-
3. Select **Save**.
26
-
27
-
- Using Terraform
28
-
1. Set `diagnose_support_enabled` to false in the `azurerm_nginx_deployment` resource.
29
-
2. Run `terraform plan` followed by `terraform apply` to upgrade the deployment.
30
-
31
-
- Using the Azure CLI
32
-
Run the following command:
33
-
```shell
34
-
az nginx deployment update --name myDeployment --resource-group \
35
-
myResourceGroup --enable-diagnostics="false"
36
-
```
20
+
3.**Migrate existing alert rules** to use Platform metrics instead of Custom metrics:
21
+
22
+
If you have existing alert rules configured for Custom metrics, you need to update them to use the equivalent Platform metrics signals.
23
+
24
+
1. In the [Azure portal](https://portal.azure.com), go to **Monitor** > **Alerts**.
25
+
2. Select **Alert rules**.
26
+
3. Select the alert rule you want to migrate, then select **Edit**.
27
+
4. In the **Conditions** tab, select the current **Signal name** to modify it.
28
+
5. Replace the Custom metrics signal with the corresponding Platform metrics signal:
29
+
- Platform metrics signals use the `NGINXaaS Standard Metrics` namespace
30
+
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.
31
+
7. Review and adjust the alert logic, thresholds, and conditions as needed.
32
+
8. Select **Review + create**, then **Create** to save the updated alert rule.
33
+
34
+
{{< 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 >}}
0 commit comments