Recording Rules

Training Overview
Introduction
Prerequisites
Recording Rules Overview
Motivation
Configuring Recording Rules
Evaluation Cycle
Rule Naming Conventions
Knowledge Check
Recording Rules Example
Configuring a Recording Rule
Inspecting Rule Evaluation States
Querying Recorded Metrics
Knowledge Check
Review and Outlook
Summary
Further Steps

Knowledge Check

What are some reasons for using recording rules?

To speed up slow queries by pre-recording the results.

To improve the efficiency and maintenance of shared expressions / queries.

To record expressions into a new metric name that can be federated.

All of the above.

How frequently does Prometheus run recording rules?

On a continuous basis, whenever new data is stored in the TSDB.

At a regular interval that is either configured globally or on a rule group level.

At a regular interval that is the same as the scrape interval for the underlying data.

None of the above.

What are some limitations of recording rules?

Recording rules may only select a maximum of 1000 series per rule.

Recording rules only create recorded results starting from the time that they are configured.

Recording rules may run a maximum of 30 seconds.

All of the above.