Component Entities and Health¶
What Are Component Entities¶
A system (system) is an aggregation concept at the business level, such as "payment system" or "order system". A system is typically supported by multiple lower-level entities, which are its component entities, including services, hosts, databases, etc.
A system itself does not directly generate monitoring data. Its health is calculated by aggregating the operational statuses of these component entities. When an unrecovered alert occurs on a component entity, it directly affects the health of the system it belongs to.
Note
If a system has no configured component entities, its health will be displayed as Unknown.
How Component Entities Affect System Health¶
Different component entities affect a system to varying degrees. Guance reflects this difference through importance: the higher the importance of a component entity, the greater the impact its alerts have on the system's health.
Base Importance Tier tier¶
Each entity has a default base importance tier, representing its criticality under normal circumstances:
| Tier | Description | Impact Weight |
|---|---|---|
| L0, Extremely Core | The most critical component in the system, cannot be interrupted | 5 |
| L1, Core | High-priority component | 3 |
| L2, Important | Important component | 1.5 |
| L3, Normal | General component | 1 |
| L4, Low Impact | Testing or auxiliary component | 0.5 |
| Missing | Entity has no tier set | 1 (treated as L3) |
Adjusting Impact Level Individually Within a System¶
Within a specific system, the importance of a component entity may differ from its default tier. For example, a database with a normal tier might be a core dependency in a particular system.
Therefore, Guance supports setting the impact level individually for component entities at the system level, overriding their default tier:
| Setting | Description |
|---|---|
inherit |
Inherit default tier. The entity uses its base importance tier in the current system. |
override |
Set individually Adjust the impact level of this entity within the current system. Options: critical: Core componentimportant: Important componentnormal: Normal componentlow: Low-impact component |
disabled |
Exclude from calculation This entity belongs to this system, but its alerts do not affect the system's health. |
How to Configure Component Entities¶
When creating or editing a system entity, maintain them in the "Relationships" section under Component Entities:
- Add Component Entity: Select entities like services, hosts, databases that constitute this system. They will be displayed in the list after being added.
- Adjust Health Impact: In the "Health Impact" column of the component entity list, click the dropdown to select the impact level.
- Remove Component Entity: Click the delete icon in the "Options" column to indicate that this entity no longer participates in the system's health calculation.
Relationship Synchronization Note
Whether you add component entities on the system side or set the belonging system on the child entity side, both sides are automatically synchronized. An entity can belong to multiple systems simultaneously, and each system independently calculates that entity's impact on its own health.