Infrastructure Change Detection¶

Infrastructure change detection continuously monitors Kubernetes resource configuration changes (such as YAML file modifications), combining version tracking and intelligent analysis to achieve compliance checks, root cause analysis for failures, and resource usage optimization. This ultimately ensures cluster security, stability, and resource efficiency.

Detection Configuration¶

Detection Frequency¶

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

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

Custom detection frequencies are also supported. Input format examples: 20m (20 minutes), 2h (2 hours), 1d (1 day).

Detection Metrics¶

Monitor metric data for various types of infrastructure.

Infrastructure Types: Deployments, Daemonsets, Services, Cron Jobs, Statefulsets.
Detection Targets:
- All: Detects whether the last reported update time of all basic objects in the workspace triggers the threshold.
- Custom: Fuzzy matches object names via wildcard.

Trigger Conditions¶

Set trigger conditions for three alert levels: Urgent, Important, and Warning. Triggers are determined by the following two scenarios:

Any ChangeRegex Match

An event is generated immediately when the status of the detected object changes in any way.

An event is generated immediately when the change condition satisfies the regex match.

For example, defining a regular expression as:

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

This means if an error entry related to CPU is generated in the detected object, event data will be generated immediately.

Other Configuration¶

For more details, please refer to Rule Configuration.

Event Viewing¶

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