> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Change 1-Minute Azure Log Alert Rules to 5-Minute Frequency

> Change Azure log search alert rules that run every minute to run every 5 minutes, at a lower price.

Azure Monitor log search alert rules are billed per monitored time series, and a rule that runs every minute costs more than one that runs every 5 minutes. Most alerts do not need to fire within a minute. nOps finds resource groups whose log search alert rules run every minute and estimates the saving from changing them to 5 minutes.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Management and governance |
| **Service** | Azure Monitor |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

One-minute frequency is often picked by default or copied between rules, and the cost adds up across many rules and time series.

## How nOps finds it

nOps reads the last 14 days of Azure Monitor billing for log search alert rules on the 1-minute meters, grouped by subscription and resource group. A rule counts when it was billed on at least 13 of the 14 days, was billed recently, and its name does not suggest critical alerting (such as critical, sev0, sev1, p0, p1, pager or urgent). The saving is the 7-day cost of the counted rules, scaled to a month, times (1 minus the 5-minute rate divided by the 1-minute rate), using the rates on your own bill. Groups paid mostly with credits and savings under \$5 a month are left out.

## Before you start

Know which alerts must page someone immediately, and permission to edit the alert rules.

## How to implement

1. List the rules in the resource group and agree with their owners which ones need a 1-minute response.
2. In the Azure portal, open **Monitor → Alerts → Alert rules**, edit each rule, and set **Frequency of evaluation** to 5 minutes.
3. Or use `az monitor scheduled-query update --resource-group RESOURCE_GROUP --name RULE_NAME --evaluation-frequency 5m`.
4. Update Terraform, Bicep or ARM templates (`evaluation_frequency` set to `PT5M`) so a later deployment does not change it back.

## Risks and considerations

* A 5-minute rule can raise its alert up to about 4 minutes later.
* Rules with critical-sounding names are left out, but check the rest: names do not always reflect severity.
* To roll back, set the frequency back to 1 minute.

## FAQs

> [accordion] Why is a resource group shown instead of each rule?
>
> Rules in the same resource group are usually owned by the same team, so nOps groups them into one recommendation and lists the rules it counted.

> [accordion] Why don't I see this recommendation for some rules?
>
> nOps prices the change from the 5-minute rate on your own bill. If you have no 5-minute log alert rules, it cannot price the change yet.

## Related

* [Move Older Log Analytics Data to Long-Term Retention](https://help.nops.io/inform/supported-recommendations/move-older-log-analytics-data-to-long-term-retention)
* [Dismiss Restored Log Analytics Tables](https://help.nops.io/inform/supported-recommendations/dismiss-restored-log-analytics-tables)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.