--- title: "Monitoring profiles" slug: "monitoring-profiles" updated: 2026-10-29T11:13:41Z published: 2026-10-29T11:13:41Z canonical: "docs.turbo360.com/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. # Monitoring profiles ## Overview A monitoring profile is a reusable set of monitoring rules that can be applied to a Business Application. Instead of defining rules individually for each resource, you configure a profile once, specifying which resource types to monitor and what thresholds or conditions to evaluate, and then map it to one or more Business Applications. Monitoring profiles work alongside monitoring rules configured directly at the Business Application level, letting you apply consistent, reusable monitoring standards across different applications without duplicating configuration. When the same rule is set in more than one of these sources on a resource, only one source evaluates it. **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. ### Business value Monitoring profiles eliminate the overhead of configuring monitoring rules resource by resource across large Business Applications. A single profile can govern monitoring for all instances of a given resource type across multiple Business Applications, making it faster to enforce consistent monitoring standards and easier to update them when requirements change. ## How it works ### Profile scope A monitoring profile defines monitoring rules at the resource type level. For each resource type included in the profile, you configure the relevant metrics or state conditions and their threshold values. When the profile is mapped to a Business Application, the rules apply to all resources of that type within that application. Rules in a profile can optionally include a note that is attached to any alert triggered by a rule violation, providing context for the team investigating the alert. ### Profile types - **User-created profiles:** profiles you define for specific monitoring requirements. - **System profile:** a default profile provided by Turbo360. It is always available for mapping and cannot be deleted. ### Profile mapping A profile is activated by mapping it to a Business Application. During mapping, you select which resource types from the profile to apply, then configure the alert settings, including notification channels and escalation policies, for that mapping. The same profile can be mapped to multiple Business Applications with different alert configurations for each. Profile mappings can be updated after the fact. Both the alert settings and the rule configuration for a mapped profile can be edited from the monitoring settings of the Business Application. ### Duplicate rule handling A resource can be monitored by its resource rules and by one or more monitoring profiles. If the same rule is set in more than one enabled source on that resource, Turbo360 picks one source to evaluate it. The other sources skip their copy, so a single issue raises one alert instead of one alert per source. Turbo360 picks the source that evaluates the rule as follows: - **Resource rules:** they evaluate the rule when resource monitoring is on for the Business Application and the resource, and the resource rules include the rule. - **Monitoring profile:** otherwise, the enabled profile whose name sorts first evaluates the rule. The sort ignores case. Two rules are duplicates when they have the same type and name. Thresholds, aggregation, and conditions 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, and every source evaluates them. A disabled profile doesn't count as a source. Because the profile name decides the order, renaming a profile can change which profile evaluates a duplicated rule. The system profile is never modified when you remove duplicate rules. You can review duplicate rules, remove the extra copies, or turn on **Allow duplicate rule evaluation** so that every source evaluates its own copy. The switch is off by default. To learn how, see [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles). ### Rules accessibility Once a profile is mapped to a Business Application, the monitoring rules it provides for each resource type are visible under **Monitoring → Monitoring profiles** within that application. This lets you see, for any given resource, which profiles are governing its monitoring and what rules are in effect. ### Profile operations Monitoring profiles support the following operations: - **Clone:** duplicate an existing profile as a starting point for a new one. Useful when you need a profile with mostly similar rules but different thresholds or resource types. - **Export:** download a profile's rule configuration as an Excel file for review or offline editing. - **Import:** create a new profile by uploading a previously exported (and optionally modified) Excel file. ### Autocorrect status For compatible resource types, a monitoring rule can include an **Autocorrect status** setting. This enables Turbo360 to automatically attempt to correct a resource's state when a rule violation is detected, without requiring manual intervention. ### User access control Access to monitoring profile management is controlled through user access policies in Business Applications. The **Monitoring profile** permission is a dedicated feature-level permission that can be granted independently of broader monitoring access. Custom roles can be configured to allow Read or Manage access to monitoring profiles, enabling teams to delegate profile management without granting full monitoring or application-level rights. Reviewing duplicate rules requires **Read** access to the **Monitoring** permission. Removing duplicate rules and changing **Allow duplicate rule evaluation** require **Manage** access to it. ## Related articles - [Managing monitoring profiles](https://docs.turbo360.com/docs/managing-monitoring-profiles) - [Rules configuration](https://docs.turbo360.com/docs/monitor-rules-configuration) - [Monitoring a Business Application](https://docs.turbo360.com/docs/business-application-monitoring) - [Escalation policies](https://docs.turbo360.com/docs/business-applications-escalation-policies) - [Understanding Business Applications](https://docs.turbo360.com/docs/understanding-business-applications)