Health Score User Guide
This topic explains how to use the entity health score feature in Cloud Monitor 2.0. It covers the health score list, inspection configuration, threshold settings, health details timeline, and impact scope analysis.
Function Overview
Cloud Monitor 2.0 displays the health status of all applications using a traffic-light system. This helps you quickly identify entities with issues. The system automatically checks application health using configured inspection rules and thresholds. When it detects anomalies, it generates health events. You can view the full health status and impact scope using the health score list, timeline, and impact scope views.
Access the Health Score View
Log on to the Cloud Monitor 2.0 console. Then go to your target workspace.
In the navigation pane on the left, click Entity Explorer.
In the upper-right corner of the page, click Health Score to switch to the health score view.
After switching successfully, the page shows the health status of all applications using a traffic-light system.
View the Health Score List
On the health score list page, you can view health status statistics and a detailed list of all applications.
Interface Description
The health score list page includes the following sections:
Top statistics bar: Shows the total number of entities, and counts for Normal, Warning, and Critical statuses.
Application list: Displays all applications as cards. Each card uses color to indicate health status:
Green: Normal. All metrics are within expected ranges. Or no health score rules are configured or enabled.
Yellow: Warning. An anomaly exists that needs attention.
Red: Critical. An urgent issue exists that may affect business operations.
Feature entry points: In the upper-right corner of the page, click Threshold Settings or Inspection Configuration to configure health score rules and thresholds.
Configure Inspection Rules
Use inspection configuration to manage health score detection rules. You can enable or disable built-in rules based on your business needs. You can also add custom alert rules.
View and Manage Built-in Rules
On the health score list page, click Inspection Configuration in the upper-right corner.
In the inspection rule configuration panel, view the list of built-in rules.
The rule list includes the following information:
Inspection Type: The category of a rule, such as fault, anomaly, or water level.
Rule name: The name of the rule.
Rule description: A description of what the rule checks.
Enabled status: A toggle switch. When enabled, the rule takes effect.
Enable or disable rules as needed.
Click the toggle switch next to a rule to change its enabled status:
Enabled: The rule takes effect. The system automatically creates a corresponding alert rule and starts detection.
Disabled: The rule becomes inactive. The system no longer checks this condition.
Note:
When you enable a rule, the system automatically creates a corresponding alert rule in the alert center. By default, these alert rules do not send notifications. They only generate health events. To receive alert notifications, configure a notification policy for the alert rule in the alert center.
For the full list of built-in rules and their descriptions, see Built-in Health Score Rules.
Add Custom Alerts
In addition to built-in rules, you can add existing custom alert rules to the health score inspection system.
In the inspection configuration panel, click Add Custom Alert.
In the dialog box that appears, select the alert rules to add to health score inspection. Then click OK.
After successfully adding a rule, alert events from that rule are included in health score evaluation.
Note:
You must first create custom alert rules in the Cloud Monitor 2.0 alert center.
The enabled or disabled status of an alert rule is synchronized between the alert center and health score inspection. If you disable a rule in the alert center, it no longer contributes to health score evaluation.
You can remove any added custom alert rule at any time.
Configuration Recommendations
For initial use, we recommend keeping all built-in rules enabled by default and adjusting them as needed after an observation period.
If a rule does not apply to your business scenario—such as JVM rules not being needed for non-Java applications—disable that rule.
For business-specific detection needs, add custom alert rules to include them in health score evaluation.
Configure Health Score Thresholds
Use threshold settings to define your own criteria for health status. By default, the system uses event severity thresholds. Advanced users can enable the risk index feature for more fine-grained evaluation.
View and Modify Event Severity Thresholds
Event severity thresholds provide the most direct way to determine health status. The system bases the health status on the severity level of health events associated with the entity.
On the health score list page, click Threshold Settings in the upper-right corner.
In the threshold configuration dialog box, view the current event severity mapping.
The default configurations are as follows:
Normal: No events.
Warning: Includes P3 (Warning) or P4 (Informational) events.
Critical: Includes P1 (Critical) or P2 (Error) events.
(Optional) Adjust the mapping based on your business needs.
For example, move P2 from Critical to Warning. In the dropdown list for the target health status, select the event severity levels to include. Then click OK.
Configure Risk Index Thresholds
The risk index is a quantified metric that reflects the overall health of an entity. It is designed for advanced users who need more fine-grained health score evaluation.
In the threshold configuration dialog box, turn on the Risk Index toggle.
After enabling it, the risk index configuration section appears.
View or modify the risk index thresholds.
The default risk index ranges are:
Normal: 0 to 10
Warning: 10 to 40
Critical: 40 to +∞
The risk index calculation considers the number of health events, their severity levels, and their duration.
Click OK to save the configuration.
Note: To restore default settings, click Restore Default Settings.
View Health Score Details
Click an application in the health score list to open its health score details page. This page has two tabs: Timeline and Impact Scope.
View the Timeline
The Timeline tab shows the history and trend analysis of health events for the application.
Interface Description
The Timeline page includes the following sections:
Event distribution pie chart: Shows the percentage of different event types (Error, Anomaly, Saturation, Change, Failure) in the selected time range.
Event trend chart: Shows how the number of health events changes over time. Use it to:
Determine whether an issue is persistent or intermittent.
Assess whether an issue is worsening or improving.
Identify when the issue first appeared.
Event timeline details: Lists all health events grouped by severity level. Each event shows the event name (the triggered rule name and related interface or instance), and a time bar (a visual representation of when the event occurred and how long it lasted).
Operations
Switch time range: In the upper-right corner of the page, select a time range to view (for example, Last 5 Minutes or Last 1 Hour).
Filter events: Enter an event name or entity name in the search box to filter displayed events.
Expand or collapse groups: Click the arrow icon next to a severity level to expand or collapse the event list for that group.
View event details: Click a specific event to view its trigger time, related metric values, and information about related interfaces or instances.
Go to entity details: In the event details, click a link to a related entity (such as an interface or instance) to go to that entity’s details page for deeper analysis.
Note: When an application is Normal and no health events are triggered, the page displays "No data available".
View Impact Scope
The Impact Scope tab shows upstream and downstream dependencies and the impact scope of the application using a topology graph.
On the health score details page, click the Impact Scope tab.
View the dependency topology graph.
The topology graph includes the following elements:
Current entity: Located at the center. Shows the application you are viewing.
Upstream dependencies: Services or components that call the current application.
Downstream dependencies: Services or components that the current application calls.
Health status: Each node uses color to show its health status.
Scenarios
Root cause analysis: When a service fails, use the Impact Scope view to check whether its downstream services also have issues. This helps locate the root cause.
Impact scope assessment: Identify which upstream services depend on the failing service. This helps assess the potential business impact.
Dependency mapping: Visualize service-to-service call relationships. This supports architecture analysis.
FAQ
Why is an application shown as red, but I did not receive an alert?
By default, alerts generated by health score inspection rules do not send notifications. They are used only for health score evaluation and UI display. To receive alert notifications, find the corresponding health score alert rule in the Cloud Monitor 2.0 alert center and configure a notification policy for it.
How often does health score detection run?
The system runs health rule checks every minute. It evaluates data from the past 5 minutes.
What is the difference between event severity thresholds and risk index?
Event severity thresholds (default): Determine the health status directly based on event severity. This method is simple, intuitive, and suitable for most users.
Risk index (advanced): Calculates a quantified score by combining the event count, severity, and duration. This method is suitable for advanced users who need more fine-grained evaluation.
How do I add an existing alert rule to health score inspection?
On the inspection configuration page, click Add Custom Alert. Then, select the alert rule to add. After it is added, events from that rule are included in the health score evaluation.