The Linux Foundation has registered trademarks and uses trademarks. © Prometheus Authors 2014-2021 | Documentation Distributed under CC-BY-4.0 Please help improve it by filing issues or pull requests. Recorded as an error in the evaluation, and as such no stale markers are The rule, active, pending, or inactive, are cleared as well. When the limit is exceeded, all series producedīy the rule are discarded, and if it's an alerting rule, all alerts for # Labels to add or overwrite for each alert.Ī limit for alerts produced by alerting rules and series produced recording rulesĬan be configured per-group. # Alerts which have not yet fired for long enough are considered pending.
# Alerts are considered firing once they have been returned for this long. # evaluated at the current time, and all resultant time series become The syntax for alerting rules is: # The name of the alert. # Labels to add or overwrite before storing the result. # time series with the metric name as given by 'record'. # evaluated at the current time, and the result recorded as a new set of The syntax for recording rules is: # The name of the time series to output to. # Limit the number of alerts an alerting rule and series a recording # How often rules in the group are evaluated. record: job:http_inprogress_requests:sumĮxpr: sum by (job) (http_inprogress_requests) Run sequentially at a regular interval, with the same evaluation time.Ī simple example rules file would be: groups: Recording and alerting rules exist in a rule group. This is especially useful forĭashboards, which need to query the same expression repeatedly every time they The original expression every time it is needed. Querying the precomputed result will then often be much faster than executing Recording rules allow you to precompute frequently needed or computationallyĮxpensive expressions and save their result as a new set of time series. Message to standard error and exits with a 1 return status.
If there are any syntax errors or invalid input arguments, it prints an error Representation of the parsed rules to standard output and then exits with When the file is syntactically valid, the checker prints a textual The promtool binary is part of the prometheus archive offered on the To quickly check whether a rule file is syntactically correct without startingĪ Prometheus server, you can use Prometheus's promtool command-line utility The changes are only applied if all rule files are well-formatted. The rule files can be reloaded at runtime by sending SIGHUP to the Prometheus The rule_files field in the Prometheus configuration. To include rules in Prometheus, create a fileĬontaining the necessary rule statements and have Prometheus load the file via Prometheus supports two types of rules which may be configured and thenĮvaluated at regular intervals: recording rules and alerting
0 kommentar(er)
