2020-04-27 23:19:27 +02:00
|
|
|
package main
|
|
|
|
|
|
|
|
import (
|
|
|
|
"context"
|
2020-11-09 23:27:32 +01:00
|
|
|
"errors"
|
2020-04-27 23:19:27 +02:00
|
|
|
"github.com/VictoriaMetrics/VictoriaMetrics/lib/prompbmarshal"
|
2021-06-09 11:20:38 +02:00
|
|
|
"time"
|
2020-04-27 23:19:27 +02:00
|
|
|
)
|
|
|
|
|
2020-06-01 12:46:37 +02:00
|
|
|
// Rule represents alerting or recording rule
|
|
|
|
// that has unique ID, can be Executed and
|
|
|
|
// updated with other Rule.
|
|
|
|
type Rule interface {
|
2021-06-09 11:20:38 +02:00
|
|
|
// ID returns unique ID that may be used for
|
2020-06-01 12:46:37 +02:00
|
|
|
// identifying this Rule among others.
|
|
|
|
ID() uint64
|
|
|
|
// Exec executes the rule with given context
|
2021-06-09 11:20:38 +02:00
|
|
|
Exec(ctx context.Context) ([]prompbmarshal.TimeSeries, error)
|
|
|
|
// ExecRange executes the rule on the given time range
|
|
|
|
ExecRange(ctx context.Context, start, end time.Time) ([]prompbmarshal.TimeSeries, error)
|
2020-06-01 12:46:37 +02:00
|
|
|
// UpdateWith performs modification of current Rule
|
|
|
|
// with fields of the given Rule.
|
|
|
|
UpdateWith(Rule) error
|
app/vmalert: extend metrics set exported by `vmalert` #573 (#654)
* app/vmalert: extend metrics set exported by `vmalert` #573
New metrics were added to improve observability:
+ vmalert_alerts_pending{alertname, group} - number of pending alerts per group
per alert;
+ vmalert_alerts_acitve{alertname, group} - number of active alerts per group
per alert;
+ vmalert_alerts_error{alertname, group} - is 1 if alertname ended up with error
during prev execution, is 0 if no errors happened;
+ vmalert_recording_rules_error{recording, group} - is 1 if recording rule
ended up with error during prev execution, is 0 if no errors happened;
* vmalert_iteration_total{group, file} - now contains group and file name labels.
This should improve control over specific groups;
* vmalert_iteration_duration_seconds{group, file} - now contains group and file name labels. This should improve control over specific groups;
Some collisions for alerts and recording rules are possible, because neither
group name nor alert/recording rule name are unique for compatibility reasons.
Commit contains list of TODOs for Unregistering metrics since groups and rules
are ephemeral and could be removed without application restart. In order to
unlock Unregistering feature corresponding PR was filed - https://github.com/VictoriaMetrics/metrics/pull/13
* app/vmalert: extend metrics set exported by `vmalert` #573
The changes are following:
* add an ID label to rules metrics, since `name` collisions within one group is
a common case - see the k8s example alerts;
* supports metrics unregistering on rule updates. Consider the case when one rule
was added or removed from the group, or the whole group was added or removed.
The change depends on https://github.com/VictoriaMetrics/metrics/pull/16
where race condition for Unregister method was fixed.
2020-08-09 08:41:29 +02:00
|
|
|
// Close performs the shutdown procedures for rule
|
|
|
|
// such as metrics unregister
|
|
|
|
Close()
|
2020-05-04 23:51:22 +02:00
|
|
|
}
|
2020-11-09 23:27:32 +01:00
|
|
|
|
|
|
|
var errDuplicate = errors.New("result contains metrics with the same labelset after applying rule labels")
|