Overview
Business Applications monitoring rules stop triggering alerts for a handful of well-known reasons: a configuration gap, a permissions issue, or a connectivity problem between the resource and Turbo360. This article identifies the most common causes and how to fix them.
Business value
Reliable monitoring is the foundation of incident response in Business Applications. Resolving monitoring failures quickly ensures your team receives timely alerts and maintains visibility over critical Azure resources, reducing mean time to detection for operational issues.
How it works
Business Applications monitoring evaluates rules on a fixed monitoring cycle. Each rule is scoped to a resource and applies a condition: availability status, state, metric threshold, query result, or API Endpoint response. When a cycle completes and a rule condition is met, Turbo360 generates an alert and routes it through the configured escalation policy.
Monitoring failures typically fall into one of these categories:
- The monitoring rule is not enabled or is misconfigured
- The resource is not associated with the Business Application
- The service principal lacks the permissions required to read the resource state
- The monitoring profile is not attached to the resource
- The escalation policy has no active notification channel
Troubleshooting
-
No alerts generated for a resource despite known failures
Cause: The monitoring rule for that resource is disabled or the rule condition does not match the failure state (e.g. the threshold is set too high).
Fix: Navigate to the Business Application > Monitoring > Rules configuration and verify the rule is enabled. Check that the condition type and threshold match the failure you are testing. Re-enable or adjust the rule and wait for the next monitoring cycle. -
Monitoring rule is enabled but no alerts appear
Cause: The escalation policy attached to the rule has no active recipients, or the notification channel (email, Teams) is misconfigured.
Fix: Navigate to the Business Application > Monitoring > Rules configuration, open the rule, and confirm the escalation policy is assigned. Go to Escalation policies and verify at least one recipient and notification channel is active. Save and re-test. -
Resource state appears healthy in the dashboard but alerts were expected
Cause: The monitoring cycle has not completed since the resource entered a failed state, or the rule has a suppression window active.
Fix: Wait one full monitoring cycle (typically 5 minutes) for the state to refresh. Check the rule for any configured suppression windows and disable them if not intentional. -
Query monitoring rule returns no results
Cause: The Log Analytics Workspace or Application Insights resource used in the query is not accessible to the service principal, or the query itself returns no rows.
Fix: Verify the service principal has Reader access to the Log Analytics Workspace or Application Insights resource in the Azure portal. Run the query directly in Azure to confirm it returns data. Correct the query or fix the permissions before re-testing. -
Monitoring profile is not evaluating any resources
Cause: The monitoring profile is not associated with the relevant resources, or the profile is not attached to the Business Application.
Fix: Navigate to Monitoring profiles and confirm the profile includes the resources you expect. Open the Business Application, go to Monitoring, and verify the correct profile is assigned. Reassign if needed and trigger a manual monitoring cycle.