The module lifecycle stage: Preview
The module has requirements for installation
Recording rules are calculated from other metrics using PromQL expressions and stored as separate time series.
Typical use cases include:
- Complex or resource-intensive queries.
- Queries that run frequently (for example, in multiple dashboards or alerts).
- Queries that create additional load on the metric storage.
Recording rules are defined in rule groups as items in the spec.rules array.
If a rule contains the record field, it is treated as a recording rule.
Types of rule groups with derived metrics
Three types of rule groups can define derived metrics:
| Rule group type | Scope | Who has access |
|---|---|---|
| System rule groups (ClusterObservabilityMetricsRulesGroup) | Cluster level | DKP administrators |
| Project rule groups (ObservabilityMetricsRulesGroup) | Project (namespace) level | Users of the corresponding project |
| Standard propagated rule groups (ClusterObservabilityPropagatedMetricsRulesGroup) | Created at the cluster level and automatically available in all projects | Users of all projects |
Rule group types:
-
System rule groups (ClusterObservabilityMetricsRulesGroup): Used to calculate derived metrics for platform-level and cluster component metrics. Created and managed by DKP administrators.
-
Project rule groups (ObservabilityMetricsRulesGroup): Used to calculate derived metrics within a specific project (namespace). Project users can create and edit them within the configured access permissions.
-
Standard propagated rule groups (ClusterObservabilityPropagatedMetricsRulesGroup): Created at the cluster level and automatically become available in all projects.