Infrastructure Change Detection¶

"Infrastructure Change Detection" continuously monitors changes in Kubernetes resource configurations (such as modifications to YAML files), combining version tracking and intelligent analysis to achieve compliance checks, root cause positioning for failures, and optimization of resource usage, ultimately ensuring the security, stability, and efficiency of clusters.

Detection Configuration¶

Detection Frequency¶

The execution frequency of detection rules. The system default includes the following frequencies:

30s
1m
5m (default display)
15m
30m
1h
6h

It also supports custom input for detection frequency, such as: 20m (20 minutes), 2h (2 hours), 1d (1 day).

Detection Metrics¶

Monitors metric data of various infrastructure types.

Infrastructure types: Deployments, Daemonsets, Services, Cron Jobs, Statefulsets;
Detection objects:
- All: Checks if the last update time of all basic objects within the workspace triggers a threshold.
- Custom: Matches object names using wildcard fuzzy matching.

Trigger Conditions¶

Set trigger conditions for three alert levels: urgent, important, and warning. These are determined by the following two scenarios:

Any ChangeRegular Expression Match

An event is immediately generated when any change occurs in the status of the detection object.

An event is immediately generated when the change condition satisfies a regular expression match.

For example: Define a regular expression as:

(?=.*CPU)(?=.*\berror\b)

This indicates that if an entry related to CPU errors is detected in the detection object, an event will be immediately generated.

Other Configurations¶

For more details, refer to Rule Configuration.

Event Viewing¶

Events triggered based on infrastructure change detection can be viewed under Events > Change Events.