Rules configuration

Overview

Configuring a monitoring rule lets you define exactly how Turbo360 evaluates an Azure resource's health, what value it tracks, the rule type applied, and the thresholds that decide when the resource is in a warning or error state.

Business value

Granular rule configuration lets you tune monitoring to match each resource's real-world behavior, reducing false alerts and ensuring violations reflect genuine issues instead of noise.

How it works

Rule types

A monitoring rule for a resource can be one of the following types:

Property: indicates the current value of the selected rule.
Metric: indicates the value obtained based on the aggregation period set in the monitoring settings at the Business Application level or Monitoring profile level.
Status: indicates one of the available values specific to each rule.
Availability Status: indicates the availability of the resource.

For a Property or Metric rule, threshold values can be any positive number. For a Metric rule, the threshold can also be set to any metric belonging to the chosen resource type. Its value is evaluated based on the aggregation period set in the monitor settings each time the rules evaluation frequency triggers an evaluation cycle.

Threshold types

You can set two types of threshold values for a rule:

Warning threshold
Error threshold

Monitor evaluation determines that a rule has been violated when its current value exceeds either threshold. The Error threshold takes priority for alert generation when both threshold values are met during the same monitoring cycle.

Selecting aggregation types

Each resource metric supports a list of aggregation types. Choose the one that best matches how you want the metric evaluated over the configured aggregation period.

Configuring rules

Monitoring rules can be configured from Business Application > Resources > [Resource] > Monitoring for resource-level rules, or from Settings > Monitoring settings > Monitoring profiles for profile-level rules. For rule types, thresholds, aggregation settings, and rule-driven actions such as auto-correction, automated tasks, and resolution notes, see Monitoring rules configuration.

Metric visualization

The usage pattern of a parent resource metric can be visualized through a chart, accessible from Business Application > Resources > [Resource] > Monitoring > [Metric]. The blue hue on a metric indicates that a data visualization is available for it. To focus the metric usage on a specific period, use the Settings option to customize the time interval. Yellow and red lines represent the warning and error threshold values for the metric. This visualization helps you understand a metric's usage pattern and adjust its threshold values more accurately, so alerts trigger only as usage approaches or exceeds your limits. This visualization is not available for rules configured through a Monitoring profile.

Explain with AI

The Explain with AI option is available for Availability Status rules, resource State rules, and Metric rules. It provides an AI-generated explanation of the selected rule directly in the monitoring configuration panel so you can understand what the rule checks, how to configure it correctly, and what to do when it fires, all without leaving Turbo360.

Note:

AI-generated content: The explanation produced by Explain rule with AI is generated by Azure OpenAI, based on the selected rule and your resource's current state at the time you open it. Review the guidance against your actual environment before applying it.

To use it, click the sparkle icon (✦) next to a rule name in the Availability status, Status, or Metrics section of the monitoring configuration panel. This is available both within an individual resource's Monitoring tab and in the Add monitoring profile or Edit Resource rules panel.

The explanation panel includes:

What this rule checks: a plain-language description of what the rule monitors and what a violation means for this resource type.
Why monitor this rule: a context-specific explanation of why this rule matters, based on the resource's current state and how it is being used.
Healthy vs unhealthy state: the expected healthy states for this resource type and what it means operationally when the violation state is reached.
Likely causes of a violation: the most common reasons this rule fires, with operational context specific to the resource type.
Recommended response on alert: suggested actions to take when this rule is violated, including automated task and escalation policy recommendations.
Expected state: the configured condition and violation state for this rule, and what each possible state value means.
Recommended setup: guidance on the correct condition and violation state to configure, with a rationale explaining why other settings may produce noisy or missed alerts.
Monitor these together: related rules and metrics worth pairing with this rule to get a fuller picture of the resource's operational state.
Common setup pitfalls: configuration mistakes that lead to false positives or missed violations for this rule type.

Warning:

Suggested thresholds are derived from typical values and may show "no activity in the last 24 hours" when a resource has been idle or recently provisioned. Review the current baseline and adjust thresholds to match your expected load before saving.

Update resource monitoring state

The monitoring state of a resource can be updated from Business Application > Resources > [Resource].

Enable monitoring enables monitoring for the resource using its configured rules or applied Monitoring profiles.
Disable monitoring completely disables monitoring for the resource, regardless of any rules configured through a Monitoring profile or individual rule configuration.

The monitoring state of resources can also be updated for multiple resources at once from Business Application > Resources, regardless of resource type: select multiple resources, click Monitor, choose the required monitoring state, then click Update.

Auto-correct resource status

Configure Auto-correct status for a compatible resource from Business Application > Resources > [Resource] > Monitoring > Rules > Auto-correct status, or set it while creating a Business Application. The resources that support the Auto-correct status rule include:

API App
APIM Product
Azure Function
Azure Function App
Databricks Compute Cluster
Databricks Delta Live Table
Event Hub
Logic App
Logic App - Standard
Logic App Workflow Standard
Service Bus Queue
Service Bus Topic
Service Bus Topic Subscription
Virtual Machine
Web App
Web Job

When Auto-correct status is configured with an appropriate value, the correction runs using that value at the specified monitoring interval whenever an error status is detected. The auto-corrected information appears alongside the alert details sent through your configured notification channels. Auto-corrected information is not displayed in the Business Application Alert history.

Automated tasks triggered by rule violation

You can configure an Automated task to run once a resource metric is violated during monitoring, from Settings > Monitoring settings > Monitoring profiles > [Profile] > [Resource] at the profile level, or from Business Application > Resources > [Resource] > Monitoring at the resource level.

Keep the following in mind when using automated tasks with monitoring rules:

This setting does not affect scheduled automated tasks, regardless of their configuration for any monitoring rule violation.
A task configured for an existing metric violation runs again only when that specific rule is violated again. It ignores any other resource rule violations occurring alongside it.
An automated task configured for a metric violation does not run if the metric is in a warning state.

Resolution notes

A resolution note is a brief description you provide for a rule violation. It is sent with the rule violation alert to your configured channels, giving responders immediate context on what to do.

Resolution notes can be configured at two levels:

Profile level: go to Settings > Monitoring settings > Monitoring profiles > [Profile] > [Resource]. A note added here affects every Business Application the profile is applied to.
Resource level: go to Business Application > Resources > [Resource] > Monitoring. Resource-level alerts include the note alongside the violation details.

Example scenario

A support engineer configures a Metric rule on a Function App's execution count, setting both a Warning and an Error threshold. They select the Average aggregation type to smooth out short spikes, then enable Auto-correct status to restart the resource automatically once it enters an error state. They also configure an Automated task to send a Teams notification when the rule is violated, and add a resolution note documenting the known cause for on-call reference.

Troubleshooting

Metric chart is not visible for a resource
Cause: The rule is configured through a Monitoring profile rather than at the resource level.
Fix: Configure the rule directly at the resource level to enable metric visualization.
Auto-correct status is not applied to a resource
Cause: The resource type is not on the supported list, or the violation has only reached the warning threshold rather than the error threshold.
Fix: Confirm the resource type supports Auto-correct status and that the rule has reached its error threshold.
A rule does not trigger despite the metric exceeding its expected value
Cause: The selected aggregation type doesn't reflect the actual usage pattern over the configured period.
Fix: Review and adjust the aggregation type for the metric to match how you expect it to be evaluated.
An automated task does not run after a metric violation
Cause: The metric is in a warning state rather than an error state.
Fix: Confirm the rule has reached its error threshold before expecting the automated task to run.

FAQs

What is the difference between Warning and Error thresholds?
Both thresholds trigger a violation when the metric value exceeds them. The difference is in alert priority: when both are breached in the same monitoring cycle, the Error threshold takes precedence for alert generation. Use Warning to get early notice of a degrading metric and Error to signal a critical condition that needs immediate action.
Can I configure rules at both the resource level and the profile level at the same time?
Yes. Resource-level rules and profile-level rules can both be active simultaneously for the same resource. They are evaluated independently on each monitoring cycle.
Does Auto-correct status work for all resource types?
No. Auto-correct status is only available for compatible resource types. See the supported list in the Auto-correct resource status section above. For unsupported resource types, the option is not shown in the Monitoring tab.
What happens when both Warning and Error thresholds are breached at the same time?
The Error threshold takes priority for alert generation. Only the error-level alert is raised; the warning alert is suppressed for that cycle.
Can I add a resolution note at both the profile level and the resource level?
Yes. A note at the profile level applies to every Business Application the profile is mapped to. A note at the resource level applies to that resource only. If both are configured, the resource-level note appears alongside the violation details in resource-level alerts.