---
title: "Monitoring FAQs"
slug: "monitoring-faqs"
updated: 2026-10-29T11:13:41Z
published: 2026-10-29T11:13:41Z
canonical: "docs.turbo360.com/monitoring-faqs"
---

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

# Monitoring FAQs

## Overview

This article answers common questions about monitoring Business Applications in Turbo360, including monitoring rules, profiles, alert delivery, and escalation policies.

### Business value

Understanding how monitoring works (and why it sometimes does not) reduces alert fatigue, speeds up incident diagnosis, and ensures your teams are notified at the right time through the right channels.

## How it works

This FAQ covers three areas: configuring monitoring rules, working with monitoring profiles, and managing alert delivery. Each answer links to the relevant documentation where a fuller procedure is available.

## FAQs

1. **What monitoring rule types are available for Business Application resources?** Business Applications supports five rule types: **Availability status**, **State**, **Metric**, **Query**, and **API Endpoint**. The rule types available for any given resource depend on the Azure resource type. Navigate to the resource inside your Business Application and open the **Monitoring** section to see the supported rule types.
2. **What is a monitoring profile and when should I use one?** A monitoring profile is a reusable set of monitoring rules that you can apply to multiple resources. Use profiles when several resources share the same monitoring requirements (for example, all Logic Apps in a production Business Application) to avoid configuring identical rules per resource. If the same rule is set in more than one enabled source on a resource, such as resource rules and a profile, only one source evaluates it. See [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles) for setup steps.
3. **How often does the monitoring engine check rule conditions?** Rule conditions are evaluated on the Rule Evaluation Frequency defined in the Business Application's monitoring settings or in the monitoring profile applied to it.
4. **Why am I not receiving alert notifications even though a monitoring rule is breached?** The most common causes are: the escalation policy is not attached to the monitoring rule; the notification channel is misconfigured or the recipient address is incorrect; or the alert state has not yet transitioned; some rule types require the condition to persist across consecutive cycles before an alert fires. Another cause is a duplicate rule: when the same rule is set in more than one enabled source on a resource, only one source evaluates it, and its alerts follow that source's notification settings. See [Managing escalation policies in Business Applications](https://docs.turbo360.com/docs/managing-escalation-policies-in-business-applications) and [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration) for setup details.
5. **Can I apply different escalation policies to different resources within the same Business Application?** Yes. Escalation policies are applied at the monitoring rule level, not at the Business Application level. Each rule can reference a different escalation policy. See [Managing escalation policies in Business Applications](https://docs.turbo360.com/docs/managing-escalation-policies-in-business-applications).
6. **What is the difference between Query monitoring and API Endpoint monitoring?** Query monitoring executes a query (for example, a Log Analytics or Azure Monitor query) and evaluates the result against a defined threshold. API Endpoint monitoring sends an HTTP request to a specified URL and checks the response status code or body. Use query monitoring for data-driven conditions; use API Endpoint monitoring to verify service availability. See [Query monitoring](https://docs.turbo360.com/docs/resource-query-monitoring) and [API Endpoint monitoring](https://docs.turbo360.com/docs/api-endpoint-monitoring).
7. **Can I temporarily disable monitoring for a resource without deleting the rules?** Yes. From the resource's monitoring section inside the Business Application, select **Pause monitoring**. In the dialog, enable the **Enable pause monitoring for the specified time** toggle, configure the time span (one-time or recurring), and click **Save**. Monitoring resumes automatically when the configured time span ends.

## Related articles

- [Monitoring a Business Application](https://docs.turbo360.com/docs/business-application-monitoring)
- [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration)
- [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles)
- [Managing escalation policies in Business Applications](https://docs.turbo360.com/docs/managing-escalation-policies-in-business-applications)
- [Query monitoring](https://docs.turbo360.com/docs/resource-query-monitoring)
- [API Endpoint monitoring](https://docs.turbo360.com/docs/api-endpoint-monitoring)