---
title: "Unexpected alerts and service map issues"
slug: "unexpected-alerts-and-service-map-issues"
updated: 2026-10-29T11:13:36Z
published: 2026-10-29T11:13:36Z
canonical: "docs.turbo360.com/unexpected-alerts-and-service-map-issues"
---

> ## 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.

# Unexpected alerts and service map issues

## Overview

Alerts and service maps in Business Applications can behave differently from what you intended when resources are shared between applications, added after monitoring was set up, or monitored with settings meant for another environment. This article covers the most common causes and how to fix them.

### Business value

Fixing these issues keeps alerts relevant to the team that owns the workflow, keeps alert volume manageable, and keeps the service map accurate when you triage an incident.

## How it works

Monitoring rules and monitoring profiles apply to the resources in a Business Application. A resource can belong to more than one Business Application, and each application evaluates the resource with its own rules. A monitoring profile applies to the resources that are in the application when you assign it.

When the same rule is set in more than one enabled source on a resource, such as the resource rules and a monitoring profile, only one source evaluates it. This is the default for every Business Application, so one issue raises one alert instead of one alert per source. If you turn on **Allow duplicate rule evaluation**, every source evaluates its own copy.

Service maps work in two ways. The default service map draws connections between resources automatically, based on Azure resource grouping. A user-created service map does not. Turbo360 places the resource icons on the canvas, and you draw the connections between them yourself.

## Troubleshooting

1. **Alerts fire for a resource that is outside the scope you intended.** Cause: You added resources to the Business Application after you configured monitoring, so the rules now apply to a wider set. Another cause is a shared resource that belongs to several Business Applications, each with its own rules. Fix: Review the resource list and the rule scope in each Business Application that contains the resource. Remove resources that should not be monitored under those rules, or adjust the rules to target specific resources. Remove the resource from any application where it has no monitoring role.
2. **Monitoring profile rules do not apply to resources you added later.** Cause: A monitoring profile applies to the resources that were in the Business Application when you assigned it. Resources added afterwards may need to be set up again. Fix: After you add resources, open the monitoring settings of the Business Application and check that the profile applies to the new resources. Reapply the profile if it does not.
3. **Too many alerts fire for a Business Application.** Cause: Rules fire on short-lived conditions, thresholds do not match the normal behavior of the resource, or you applied the same monitoring profile to production and non-production applications. Another cause is the same rule set in more than one source while **Allow duplicate rule evaluation** is on, so each source raises its own alert for one issue. Fix: Adjust thresholds to the baseline you observe. Where the rule supports it, require the threshold to be breached across several consecutive monitoring cycles before the rule fires. Create separate monitoring profiles for production and non-production, and move low-signal conditions from critical to warning. To remove duplicate alerts, go to **Monitoring > Settings** and turn off **Allow duplicate rule evaluation**, or open the **Duplicate rules** dialog and remove the extra copies. For steps, see [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles).
4. **The service map does not show the connections you expect.** Cause: You are using a user-created service map, which does not draw connections automatically. Another cause is that not every resource in the workflow is in the same Business Application. Fix: Open the service map and check that every resource in the workflow is on the canvas. Draw the connections between the resource icons manually. If a resource is missing, add it to the Business Application first.

## Related articles

- [Monitoring a Business Application](https://docs.turbo360.com/docs/business-application-monitoring)
- [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles)
- [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration)
- [Configuring a service map](https://docs.turbo360.com/docs/configuring-service-map)
- [Automated resource association](https://docs.turbo360.com/docs/automated-resource-association)
- [Monitoring strategy](https://docs.turbo360.com/docs/monitoring-strategy)
- [Resource grouping](https://docs.turbo360.com/docs/resource-grouping)