Monitoring rules configuration
  • 02 Sep 2022
  • 5 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Monitoring rules configuration

  • Dark
    Light
  • PDF

Introduction

Monitoring is essential to keep an eye on Serverless components to understand if they are functioning as expected.

While all the resources that constitute a line of business can be associated with a Business Application in Serverless360, it is required to configure rules on the resource level, by which the monitor will be monitoring the associated resources at the rules evaluation frequency (set in Business Application's Monitor settings) and send's a consolidated report to the chosen notification channels and email recipients.

Types of rules

The rule of a resource can be of any of the following types:

1. Property
2. Metric
3. Status

Property indicates the current value of the selected rule.

Metric indicates the value that is obtained based on the aggregation period (set in the monitoring settings at Business Application level (or) Monitoring profile level).

Status indicates one of the available values (specific to each rule).

Added Information

  • For a rule of type Property or Metric, threshold values can be any positive number.

  • For a rule of type Metric, threshold values not only can be a number but can also be any metric belonging to the chosen resource type, whose value will be evaluated based on the aggregation period set in the Business Application's monitor settings when the monitor starts its evaluation process based upon the rules evaluation frequency.

Types of Thresholds

Users can set two types of threshold values for one rule:

1. Warning threshold
2. Error threshold

Added Information

  • Monitor evaluation determines that a rule has been violated when its current value exceeds one of the threshold values.

  • Error threshold is given priority upon alert generation when both threshold values are met during monitoring.

Rules configuration

The rules for all associated Azure resources in a Business Application can be configured in two ways:

  • Configure monitoring rules at Business Application level
  • Use of Monitoring profile to configure rules at the Resource level

Configure monitoring rules at the Business Application level

Users can configure rules for resources of all types while creating a Business Application (or) configuring rules for individual resources at the Business Application level.

  1. While creating a Business Application, choose Configure monitoring rules option under the Monitoring rules step and configure the rules for individual resources associated with the corresponding Business Application.

Create BA - Configure rules.png

  1. The monitoring rules can also be configured for individual resources under the Monitoring tab within each associated resource.

The image shown below is the monitoring rules available for an APIM Product resource:

APIM Product.png

Update resource monitoring state

The resource level monitoring for the associated Azure resources can be enabled or disabled at any point of time either individually or in bulk.

Users can enable the resource monitoring for any resource by clicking the Enable monitoring option available within each associated resource. Clicking this option will enable monitoring for the respective resource with the help of configured monitoring rules or via applied Monitoring profiles.

The image shown below is the Enable monitoring option available for an API App resource:

Enable monitoring.png

The resource monitoring can be disabled for any resource by clicking the Disable monitoring option available within each associated resource. Clicking this option will disable monitoring for the respective resource, irrespective of the rules configured using the Monitoring profile or by individual rules configuration.

The image shown below is the Disable monitoring option available for Azure Function resource:

Disable monitoring.png

Bulk operation

The Enable & Disable operations can also be performed in bulk for multiple resources of different resource types. This can be achieved by selecting the required resources from the Resources section and choosing the required option from the Monitor breadcrumb option.

bulk monitor.gif

Auto correct resource status

Business Applications product allows users to automatically correct resource status without navigating to the Azure portal. This new feature relieves users with the need to check the status of resources regularly and manually modify them.

Users can set the Auto-correct status of compatible resources by configuring it when creating a Business Application or by switching to the Monitoring section of the compatible resources.

Given below is the image of setting auto-correct status for a Logic App resource when creating a Business Application:

Auto correct - Create BA.png

The image shown below displays the auto correct status option available within an Event Hub resource:

Auto correct - resource level.png

The list of resources that support the monitoring rule of Auto correct status includes:

  • API App
  • APIM Product
  • APIM API
  • APIM Operation
  • Azure Function
  • Azure Function App
  • Event Hub
  • Logic App
  • Logic App - Standard
  • Logic App Workflow Standard
  • Service Bus Queue
  • Service Bus Topic
  • Service Bus Topic Subscription
  • Virtual Machine
  • Web App
  • Web Job

When the Auto correct status rule is given an appropriate value for a resource, the auto-correction operation will be performed using the provided status value in the specified monitoring time interval if an error status is detected.

The auto-corrected information will be displayed along with the alert details generated through the configured Notification channels when an error status is detected.

The image shown below displays the auto-corrected information of the Event Hub resource received through Serverless mail:

Auto correct message.png

The auto-corrected information of resources will not be displayed in the Business Application Alert history.

Automated task with rule violation

  • Users can configure an Automated task available in a Business Application with a resource metric to run the task once the corresponding metric is violated while monitoring.

  • This is possible using both the monitoring profile and the individual resource level rules configuration methods of resource monitoring.

Monitoring profile level

Given below is an image of the profile applied to a Business Application in which the user is configuring task for a rule violation at a profile level with respect to a resource.

AT integration - profile level.png

Resource level

The image shown below displays the automated task configuration for a rule violation at resource level.

AT integration - resource level.png

  • It will not affect scheduled automated tasks regardless of the task configuration for any monitoring rule violation of Azure resources.

  • The configured automated tasks for existing metric violations will only run when there is a new violation for that rule regardless of any new resource rule violations included with the existing rule violation.

The automated task configured for any metric violation will not run if the corresponding metric is in a warning state while monitoring the respective resource.


Was this article helpful?