- 04 Sep 2023
- 6 Minutes to read
Monitoring a Business Application
- Updated on 04 Sep 2023
- 6 Minutes to read
Serverless360 understands problems faced by enterprises and offers an out-of-the-box monitoring solution that helps users to monitor the distributed Azure Services grouped in an integrated solution.
An enterprise-integrated solution may contain multiple Azure services being used, and these resources from various subscriptions can be grouped in a Serverelss360 Business Application to make more meaningful monitoring.
Business Application monitor allows users to monitor the state and metrics of their Azure resources, assisting in the improvement of overall performance and Azure resource usage.
Monitoring settings provide the following options to be configured based on the user's needs. These options are common in all places wherever a user is required to configure the monitoring settings:
Set the timezone based on which resource monitoring should be performed for a particular Business Application.
In terms of monitoring frequency, the following options are available in the monitoring configuration:
Rules evaluation frequency - All the resources associated with the chosen Business Application will be monitored based on this frequency.
Aggregation period - All the metrics of the resources associated with the chosen Business application will be aggregated using the metric's Primary Aggregation Type, based on the Aggregation Period provided.
Monitor scaled app service instances - The scaled instances as well as the default instances for Web apps, Function apps, and App service plans are monitored when this checkbox is enabled.
Violation report settings
The following settings should be configured in the monitor settings to specify when monitoring should be carried out:
Days - All the monitoring alerts for the provided frequency and aggregation period will be generated only on the mentioned days of the week.
Hours - All the monitoring alerts for the provided frequency and aggregation period will be generated only on the mentioned hours in a day.
Include healthy rules in the report - Violation reports of a Business Application can be configured to include the healthy rules along with the violated rules of the monitored resources.
Include all identified issues - By default, issues reported already will be ignored in the consecutive alerts. Enabling this option will include all the identified issues in the alert.
Status report settings
A status report provides a detailed report on the status of a user's Azure resources for aggregated data over the specified aggregation period in the selected hours. The status report for a Business Application will be generated only on the mentioned hours in a day for the provided frequency and aggregation period.
Users can configure to receive status reports only when there is any error status on the monitored rules by enabling the provided checkbox.
The status alert time period is completely independent of the rules evaluation frequency.
Monitoring alert settings
Under this category, all configured notification channels are listed and email address(es) is/are specified to receive violation notifications and status reports.
Alerts are generally sent to mentioned email addresses. Users can configure more than one email address and can also choose if the alerts can be sent to all the email addresses in a single go or as separate emails.
Recipients can be configured in two ways:
Comma-separated(,) Emails - Send separate alerts to all email addresses. Each email delivered to a recipient is counted as a separate email count.
Semicolon-separated(;) Emails - Send a single alert to all email addresses in one go. A single email count is considered here.
Besides email alerts, third-party Notification channels can also be configured to receive alerts from Serverless360. Notification channels that are already configured in the Settings section, can be chosen from the displayed list.
- When both the Recipients and Notification channels are not configured, the resources will be monitored without any notifications being sent.
- The status of the resources that are monitored will be reflected in the Business Application card, Resources section, and Service Map section.
Considering the variety of monitoring services provided by the Serverless360 product, monitoring can be performed in two different ways.
The two ways include:
- Configure rules at the Resource level
- Map a Monitoring profile to a Business Application
This article covers resource monitoring by configuring rules at the resource level in detail.
Resource level monitoring
All the resources associated with a Business Application can be monitored by configuring rules and monitoring configurations while creating a Business Application (or) with the help of the Monitoring tab available within each associated resource.
- While creating a Business Application, Choose the Configure monitoring rules option under the Monitoring rules step and configure the necessary rules for each resource.
- The next step is the alert configuration for rules configured in the previous step. Configure alert settings and then proceed with the Business Application creation process. A similar process applies to the Edit Business Application flow.
- The alert configuration for rules configured at the resource level can also be customized by using the General settings under the Monitoring tab available within the respective Business Application. Monitoring using rules configured at the resource level can be Enabled (or) Disabled from the Monitoring settings section of the respective Business Application.
Enabling/Disabling monitoring from the Monitoring settings section of a Business Application will not affect the monitoring profiles that are mapped to it.
Controlling monitoring state of a Business Application
Resource monitoring in a Business Application can be controlled from different areas based on the kind of monitoring configured to it:
- Enabling/Disabling monitoring from the General settings in the Monitoring section of a Business Application will enable/disable resource monitoring for which the rules are configured at each resource level.
- Enabling/Disabling monitoring for a particular profile from the Monitoring profile settings in a Business Application will enable/disable resource monitoring only for the corresponding profile mapped to it.
- Enabling/Disabling monitoring via the Business Application Overview will completely enable/disable resource monitoring for the particular Business Application, regardless of the number of monitoring profiles configured.
The status of rules monitored for the associated resources can be viewed by clicking on each resource's monitor status from the corresponding resource type section (or) within the respective Business Application's Resources section.
The monitoring status from various profiles will have a Header as the name of the respective profile whereas the status from individual rules configuration will have a Header as Rule status.
The image shown below displays the monitor status of a Cosmos SQL Container resource for which the monitoring rules are configured at resource level and by using system profile:
Users can access the historical summary of the Business application's alert status in the form of a calendar. Data for the last 30 days will be always available to users for reference.
- The summary of all Business Applications can be notified to users through Notification channels and email address(es) at the specified hours. This can be achieved by enabling Summary Alert for Business Applications from the Serverless360 Homepage.
The alert includes information on the list of monitored Business Applications along with the resource count for each monitoring state.
Clicking on the Business Application name in the Summary Alert navigates the user directly to the Overview section of the corresponding Business Application. This navigation is available only in the email notification.
The below image displays the Summary alert for Business Applications received through Serverless360 mail:
A user with a Contributor (or) Owner role can only update the Summary Alert configuration for the Business Applications.