Activity log monitoring

Overview

Activity log monitoring lets you track significant Azure Activity Log entries for resources within a Business Application that can affect Azure health or cost. Turbo360 surfaces these entries as configurable rules — at the individual resource level or across a monitoring profile — so you can catch impactful operations without checking the Azure portal directly.

Business value

Activity log monitoring eliminates the need to manually review the Azure Activity Log per resource. Configure rules once and receive proactive alerts when an operation breaches an expected threshold, reducing the time it takes to detect Azure health or cost-impacting changes.

Prerequisites

The resource must be associated with a Business Application. The following tier-1 resource types support full management and monitoring operations, including activity log monitoring:

Required permissions

Permission requirements differ depending on where the activity log rule is configured:

• Resource-level rules — requires at least Read access on the resource, plus Manage permission on the resource's Monitoring feature.
• Profile-level rules — requires Manage permission on the Monitoring profiles feature. This permission is assigned through custom role creation (RBAC) in the Business Applications module.

How it works

• Compatible resources expose an Activity logs tab under their Monitoring section, where you can add rules from a set of available categories and operations.
• Activity logs is also available as a rule category when configuring rules through a monitoring profile, so a single profile can apply activity log rules across multiple resources of the same type.
• An alert is triggered when a configured operation's status breaches the expected error threshold you've set.
• Rules can be configured independently at resource level and at profile level. A resource can have both; profile-level rules apply to every resource of that type linked to the profile.

Steps

Use the following steps to configure activity log rules at the resource level or across multiple resources using a monitoring profile. Navigate to the resource's Monitoring section in the tree view to get started.

Configure a resource-level rule

Configuring a rule at the resource level monitors a specific operation for that resource only.

1. Open the resource and navigate to its Monitoring section.
2. Select the Activity logs tab.
   
3. Choose a category and the specific operation you want to monitor.
4. Set the expected error threshold for the operation.
5. Select Save.

Configure a profile-level rule

Configuring a rule at the monitoring profile level applies it to every resource of that type linked to the profile, eliminating per-resource setup.

1. Open the monitoring profile for the relevant resource type.

2. Select Activity logs as the rule category.
   

3. Choose the category and operation, then set the expected error threshold.

4. Select Save.

Configuration

Example scenario

For an Integration Account, you configure an activity log rule to monitor a specific operation category. When that operation's status breaches the configured error threshold, Turbo360 triggers a violation alert so you can investigate before the issue affects downstream processes.

Permission behavior

Resource-level rules: With Read access on the resource and Manage permission on its Monitoring feature, you can create, edit, and delete activity log rules for that resource. With Read permission only, you can view existing rules but cannot modify them.

Profile-level rules: Configuring activity log rules through a monitoring profile requires Manage permission on the Monitoring profiles feature. This is assigned via custom role creation (RBAC) in the Business Applications module. Without this permission, profile-level rule configuration is unavailable.

Troubleshooting

1. Monitoring value shows as NA
   Cause: The configured activity log operation isn't available for that resource in Azure.
   Fix: Choose a different supported operation, or verify in the Azure portal whether the operation applies to this resource type.
2. Activity logs tab or rule options are read-only
   Cause: Your account has only Read permission on the resource's Monitoring area.
   Fix: Request Manage permission for Monitoring on that resource from your administrator.

FAQs

1. Can I configure activity log rules at both the resource level and the monitoring profile level?
   Yes. Resource-level rules apply to that single resource only. Profile-level rules apply to every resource of that type linked to the profile. Both can be active at the same time.
2. What happens if an activity log operation isn't available in Azure for a resource?
   The monitoring value for that operation is shown as NA.
3. What permissions do I need to configure activity log rules?
   It depends on where you are configuring the rule. For resource-level rules, you need at least Read access on the resource plus Manage permission on its Monitoring feature. For profile-level rules, you need Manage permission on the Monitoring profiles feature, assigned via custom role creation (RBAC) in the Business Applications module.

Related articles

• Rules configuration
• Managing monitoring profiles
• Query monitoring
• API Endpoint monitoring
• Managing escalation policies in Business Applications