--- title: "Managing monitoring profiles" slug: "managing-monitoring-profiles" updated: 2026-11-05T09:53:38Z published: 2026-11-05T09:53:38Z canonical: "docs.turbo360.com/managing-monitoring-profiles" --- > ## 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. # Managing monitoring profiles ## Overview A monitoring profile lets you define a reusable set of monitoring rules for specific Azure resource types, independent of the rules configured at the Business Application level. You create a profile once and map it to any Business Application to apply consistent monitoring across all matching resources. ### Business value Configuring monitoring rules resource-by-resource doesn't scale once a Business Application contains many resources. Monitoring profiles let you define rules once per resource type and apply them in bulk, reducing setup effort and keeping monitoring consistent across resources. ## Prerequisites You need an existing Business Application with resources added before you can map a monitoring profile to it. ### Required permissions You need the **Monitoring profile** permission to work with monitoring profiles: - **Read:** allows you to view monitoring profiles. - **Manage:** allows you to create, edit, clone, import, export, and map monitoring profiles. Reviewing and removing duplicate rules, and changing the **Allow duplicate rule evaluation** switch, use the **Monitoring** permission instead. **Read** lets you see duplicate rules, and **Manage** lets you change them. ## How it works **Note:** A rule that is set in more than one enabled source on the same resource is evaluated by only one of them, so a single issue raises one alert. This applies to every Business Application. Your rules don't change. To let every source evaluate its own copy, turn on **Allow duplicate rule evaluation** for the Business Application. - A monitoring profile groups monitoring rules (metric-based or state-based) by Azure resource type. - Each profile can include rules for multiple resource types in a single definition. - Mapping a profile to a Business Application applies its rules to every matching resource in that Business Application at once. - A resource type shows a tick mark in the **Add monitoring profile** panel once rules are configured for it. - The **Auto correct status** rule is available only for compatible resource types. - When the same rule is set in more than one enabled source on a resource, only one source evaluates it. Resource rules evaluate it if resource monitoring is on. Otherwise, the enabled profile whose name sorts first (ignoring case) evaluates it, and the other sources skip their copy. - Two rules are duplicates when they have the same type and name. Thresholds aren't compared, so only the threshold of the source that evaluates the rule applies. - Activity log, Query, and Expiration rules are never treated as duplicates. Every source evaluates them. - A disabled profile doesn't count as a source, and the system profile is never changed when you remove duplicates. - Renaming a profile can change which profile evaluates a duplicated rule. ## Steps Navigate to **Monitoring settings > Monitoring profiles** to get started. ### Add a profile Adding a profile creates a named, reusable rule set you can map to one or more Business Applications. 1. Go to **Monitoring settings > Monitoring profiles** and click **Add.** 2. Enter a unique profile name and a description to distinguish it from other profiles. 3. Select the monitoring metrics for the required resource types and configure the threshold values. Click the **sparkle icon ( ✦ )** next to a monitoring rule under any rule category to open the **Explain with AI** panel, which provides AI-generated guidance on what the metric measures, suggested thresholds, recommended aggregation type, and common setup pitfalls for that rule. 4. Optionally, add a note to attach with rule violations. 5. Click **Save**. ### Update a profile Updating a profile lets you revise its name, description, or rules and push the changes to every Business Application it is already mapped to. 1. Go to **Monitoring settings > Monitoring profiles**. 2. Click the **Edit icon** next to the profile you want to change. 3. Update the profile name or description on the first page, then click **Next**. 4. Update or add rules for any resource type, then click **Next**. 5. Review the Business Applications the profile is mapped to, select them, and click **Save** to apply the changes. ### Delete a profile Deleting a profile permanently removes it and unmaps it from any Business Application it was applied to. 1. Go to **Monitoring settings > Monitoring profiles**. 2. Click the **Delete icon** next to the profile you want to remove. 3. Click **Delete** in the confirmation dialog. ### Clone a profile Cloning creates a copy of an existing profile, preserving its rule set as a starting point for a new profile without rebuilding rules from scratch. 1. Go to **Monitoring settings > Monitoring profiles**. 2. Click the **Clone icon** next to the profile you want to copy. 3. Enter a name for the cloned profile and click **Save**. ### Export and import profiles Exporting and importing lets you review and update profile rules in bulk using Excel, rather than editing each rule in the UI. 1. Go to **Monitoring settings > Monitoring profiles**. 2. To export, click **Export** next to **Delete** under **Actions** to download the profile as an Excel file. 3. To import, click **Import**, select the Excel workbook, enter a profile name, and click **Next**. 4. Choose the resource types, configure the rules, and click **Import** to add the profile to your Business Applications. ### Map a profile to a Business Application Mapping a profile applies its rules to every matching resource type within the selected Business Application in a single action. 1. Go to **Business Application > Monitoring > Profile settings**. 2. Click **Apply profile**. You'll see all user-created profiles and the system profile available to map. 3. Select the resources whose monitoring rules you want applied from the profile. 4. Click **Next**. 5. Configure the monitoring alert settings for the profile. 6. Click **Save**. You can update the alert settings and rules for a mapped profile anytime from the **Actions** column for that profile. **Points to remember:** - Only resource types that have monitoring rules in the profile are listed when you configure resources during mapping. - Removing a profile from a Business Application only affects that Business Application; the profile itself isn't deleted. ### Review duplicate rules Reviewing duplicate rules shows which rules are set in more than one enabled source on a resource, such as **Resource rules** and monitoring profiles, and which source evaluates each one. 1. Open the Business Application and go to **Overview**. When duplicates exist and **Allow duplicate rule evaluation** is off, the **Monitoring** card shows a **Duplicate rules configured** link with a warning icon. 2. Click the link, or go to **Monitoring > Settings**. The duplicate rules strip shows a pill with the number of duplicates, such as **1 duplicate rule** or **2 duplicate rules**. It is hidden when there are no duplicates. 3. Click the pill to open the **Duplicate rules** dialog. Each row is a duplicated rule, grouped by resource, with the columns **Rule**, **Type**, **Configured in**, and **Keep in**. 4. Check **Configured in**. It lists the sources in evaluation order, such as **Resource rules** and monitoring profile names, and the first source is the one that evaluates the rule today. ### Remove duplicate rules Removing duplicates keeps one copy of each selected rule and deletes the copies from the other sources of that resource, whether those are **Resource rules** or monitoring profiles. 1. In the **Duplicate rules** dialog, select the rows you want to clean up. Use the row checkboxes, or the select-all checkbox. 2. For each selected row, choose the source to keep in **Keep in**. The list includes **Resource rules** and the monitoring profiles the rule is configured in. It defaults to the source that evaluates the rule today, so only copies that are already skipped are removed. 3. Click **Remove duplicates**. 4. In the **Remove duplicate rules** confirmation, review the summary of rules to be removed and the sources they are removed from, then click **Remove**. 5. The duplicate list reloads, and the dialog closes when no duplicates remain. **Points to remember:** - Rules are removed from a monitoring profile or from **Resource rules** only for this resource in this Business Application. The profile itself, other resources, and other Business Applications aren't changed. - The system profile can't be modified, so any copy in the system profile stays. If every copy you would remove is in the system profile, **Remove** is disabled. - The system profile contains preset rules that can't be edited or removed, so a copy in the system profile always stays. To resolve a duplicate in favour of the system profile, choose it in **Keep in**. To stop a resource from using the system profile, turn off **Monitor** for the system profile on that resource. - If a profile has no rules left for a resource, the resource is removed from that profile for this Business Application. If it was the last resource of the profile, the profile is unmapped from the Business Application. - A later edit to a profile can bring a rule removed from that profile back. ### Allow or stop duplicate rule evaluation The **Allow duplicate rule evaluation** switch decides whether a duplicated rule is evaluated once or in every source for the Business Application. It is off by default. 1. Go to **Business Application > Monitoring > Settings**. 2. Click the **Allow duplicate rule evaluation** switch. The switch doesn't change until you confirm. 3. Read the confirmation, then click **Continue**. Click **Cancel** to keep the current behavior. - Turning the switch on: the confirmation explains that a rule set in more than one source is evaluated in every source, so the same issue can alert more than once. - Turning the switch off: the confirmation explains that a rule set in more than one source is evaluated once, with resource rules first and then monitoring profiles. 4. The change applies from the next monitoring run. While the switch is on, the **Duplicate rules configured** link is hidden on **Overview**, and the pill on **Settings** stays visible. ## View applied profile rules You can check which rules apply to a resource through any mapped profile under **Monitoring > Monitoring profiles**. On the **Monitoring** tab of a resource, the note **Monitored through** lists the sources that monitor the resource. **Resource rules** appears first when any resource rule is monitored, followed by the mapped profiles in the order that decides which one evaluates a duplicated rule. When a resource has more than one source, the note also states whether duplicate rules are evaluated once or in each source. ## Include or exclude a resource from profile monitoring When a profile is applied at the Business Application level and has monitoring rules for a resource, you can use the **Monitor** toggle to control whether that specific resource is included in or excluded from monitoring under that profile. 1. Open the Business Application and go to **[Resource] > Monitoring > Monitoring profiles**. 2. Locate the applied profile whose monitoring scope you want to adjust. 3. Use the **Monitor** toggle next to the profile to include or exclude the resource from monitoring under that profile: - Toggle **on:** the resource is monitored using the rules defined in the profile. - Toggle **off:** the resource is excluded from monitoring for that profile. Rules from the profile are not evaluated for this resource. **Note:** The **Monitor** toggle controls participation at the individual resource level only. It does not affect other resources in the same Business Application or the profile itself. The toggle is also available for the system profile. ## Permission behavior - With **Read** access, you can view existing monitoring profiles and the rules they contain, but you can't create, edit, or map them. - With **Manage** access, you can create, edit, clone, import, export, and map monitoring profiles to Business Applications. - With **Read** access to the **Monitoring** permission, you can see the **Duplicate rules configured** link, the duplicate rules pill, and the **Duplicate rules** dialog. Without it, the link and the pill stay hidden. - With **Manage** access to the **Monitoring** permission, you can change **Allow duplicate rule evaluation** and use **Remove duplicates**. Without it, both controls are disabled. ## Example scenario A Business Application contains dozens of Function Apps and Logic Apps that all need the same metric and state-based monitoring rules. Instead of configuring each resource individually, you create a single monitoring profile with rules for both resource types and map it to the Business Application, applying consistent monitoring to every matching resource in one action. ## Troubleshooting 1. **Profile rules aren't applying to a resource** Cause: the resource type wasn't selected when the profile was mapped to the Business Application. Another cause is that the same rule is set in a source that evaluates it first, such as resource rules, so the profile skips its copy. Fix: open the profile mapping for the Business Application, select the resource type, and save. To check for duplicates, open **Monitoring > Settings** and review the **Duplicate rules** dialog. 2. **Imported profile is missing expected rules** Cause: the exported Excel file was edited in a way that broke the expected resource type or rule structure. Fix: re-export a fresh template, make changes carefully without altering the structure, and re-import. 3. **Auto correct status isn't triggering for a resource** Cause: Auto correct status is only available for compatible resource types, and this resource type may not support it. Fix: check whether the resource type supports Autocorrect status before relying on it in the profile. 4. **Updated profile rules aren't reflected on an already-mapped Business Application** Cause: editing a profile doesn't automatically push changes to existing mappings. Fix: open the Business Application's monitoring settings and update the mapping for that profile. 5. **Can't delete a profile** Cause: the system profile is a default profile provided by Turbo360 and can't be deleted. Fix: only user-created profiles can be removed; use Clone if you need a customised, deletable version. ## FAQs 1. **What's the difference between a monitoring profile and resource-level rules set directly on a Business Application?** A profile is a reusable rule set you define once and map to one or more Business Applications. Resource-level rules set directly on a Business Application apply only to that application. If the same rule is set in both, only one source evaluates it. Resource rules evaluate it when resource monitoring is on, unless you turn on **Allow duplicate rule evaluation**. 2. **Can the same monitoring profile be mapped to more than one Business Application?** Yes. The same profile can be mapped to multiple Business Applications, each with its own alert configuration. 3. **What is the system profile?** The system profile is a default monitoring profile provided by Turbo360. It's always available for mapping and can't be deleted, unlike user-created profiles. ## Related articles - [AI Agents in Business Applications](https://docs.turbo360.com/docs/ai-agents-in-business-applications) - [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration) - [Monitoring a Business Application](https://docs.turbo360.com/docs/business-application-monitoring) - [Managing escalation policies in Business Applications](https://docs.turbo360.com/docs/managing-escalation-policies-in-business-applications) - [Managing Business Applications](https://docs.turbo360.com/docs/managing-business-applications)