Configuring monitoring profiles

Prev Next

Overview

This tutorial walks you through configuring monitoring profiles in Business Applications from end to end. You will create a monitoring profile with rules for specific Azure resource types, map it to a Business Application, and verify that the rules are applied. By the end of this tutorial, your Business Application will have consistent monitoring across all matching resources without needing to configure each resource individually.

Business value

Configuring monitoring rules directly on each resource does not scale as your Business Applications grow. Monitoring profiles let you define rules once per resource type and apply them to any number of Business Applications in a single mapping action, reducing setup time, eliminating rule drift, and making it easy to update monitoring standards centrally.

Prerequisites

Before you begin, make sure you have:

  • At least one Business Application with resources already associated
  • An understanding of the metric and state-based monitoring rules available for your resource types

Required permissions

You need the Monitoring profile permission to work with monitoring profiles:

Permission level What you can do
Read View monitoring profiles and the rules they contain
Manage Create, edit, clone, import, export, and map monitoring profiles

How it works

A monitoring profile is a reusable collection of monitoring rules grouped by Azure resource type. You create the profile once in Monitoring settings, then map it to one or more Business Applications. When you map a profile to a Business Application, Turbo360 applies its rules to every resource in that application whose type is covered by the profile. Profiles and Business Applications are independent; removing a profile from an application does not delete the profile, and updating a profile after mapping requires a manual re-apply to push changes to existing mappings.

Steps

This tutorial takes you through creating a profile, mapping it to a Business Application, and verifying the applied rules. Navigate to Monitoring settings > Monitoring profiles in Turbo360 to get started.

Step 1: Create a monitoring profile

Creating the profile defines the rule set that you will apply to one or more Business Applications.

  1. Go to Monitoring settings > Monitoring profiles.
  2. Click Add profile.
  3. Enter a unique profile name and a short description that identifies its purpose (for example, Integration Platform — Production or Logic App Health Checks).
  4. Click Next.
  5. In the rules configuration section, locate the resource types you want to cover. Select the monitoring metrics for each resource type and configure the threshold values (for example, a Logic App run failure rate above 5%).
  6. Optionally, add a violation note to attach to any alert raised by a rule in this profile.
  7. Click Save.
Note:

A tick mark next to a resource type in the profile panel indicates that rules have been configured for it. The Auto correct status rule is available only for compatible resource types.

Step 2: Map the profile to a Business Application

Mapping applies the profile's rules to every resource in the target Business Application whose type matches a configured rule set in the profile.

  1. Navigate to the Business Application you want to monitor.
  2. Go to Monitoring > Profile settings.
  3. Click Apply profile.
  4. Select the profile you created in Step 1.
  5. In the resource selection panel, select the resource types whose monitoring rules you want applied from this profile.
  6. Click Next.
  7. Configure the alert settings for this mapping; set the notification schedule, add alert recipients, and optionally configure a status report schedule.
  8. Click Save.
Note:

Only resource types that have monitoring rules configured in the profile appear in the resource selection panel during mapping.

Step 3: Verify applied rules

Verifying the rules confirms that the profile was mapped correctly and that each target resource is covered.

  1. In the Business Application, go to Monitoring > Monitoring profiles.
  2. Locate the profile you just mapped. The Actions column shows options to update alert settings or remove the mapping.
  3. Click on a resource listed under the profile to view the specific rules applied to it.

Allow one monitoring cycle to complete. The Business Application dashboard will reflect each resource's health state based on the newly applied rules.

(Optional) Update the profile rules

If you need to adjust thresholds or add rules for additional resource types, update the profile and re-apply the mapping to push changes to the Business Application.

  1. Go to Monitoring settings > Monitoring profiles.
  2. Click the Edit icon next to the profile.
  3. Update the profile name, description, or rules as needed. Click Next at each stage.
  4. On the final screen, select the Business Applications the profile is mapped to and click Save to apply the updated rules.

Troubleshooting

  1. Profile rules are not applying to a resource after mapping
    Cause: The resource's type was not selected during the mapping step.
    Fix: Open the profile mapping for the Business Application under Monitoring > Profile settings, select the missing resource type, and save.

  2. Updated profile rules are not reflected on an already-mapped Business Application
    Cause: Editing a profile does not automatically push changes to existing mappings.
    Fix: Open the Business Application's Monitoring > Profile settings, locate the profile, and click Update in the Actions column to re-apply with the new rules.

  3. The profile I created does not appear in the Apply profile panel
    Cause: The profile may still be loading, or it was created under a different organization context.
    Fix: Refresh the page. If the profile still does not appear, verify you created it under the correct organization.

  4. Auto correct status rule is not triggering
    Cause: The Auto correct status rule is only available for compatible resource types, and the resource type you are targeting may not support it.
    Fix: Check whether the resource type supports Autocorrect status in the rules configuration section before relying on it in the profile.

  5. Monitoring data is not appearing after mapping
    Cause: The first monitoring evaluation cycle has not yet completed since the profile was mapped.
    Fix: Allow one full monitoring cycle to complete. The evaluation frequency is set in the alert configuration for the mapping.

Related articles