mirror of https://github.com/etcd-io/etcd.git synced 2024-09-27 06:25:44 +00:00

Files

Björn Rabenstein c9a5889915 Documentation/etcd-mixin: Reformulate alerting rules to use without rather than by (#12122 )

* etcd-mixin: Reformulate alerting rules to use `without` rather than `by`

With aggregations using `by`, all additional target labels that a user
might have configured, are aggregated away. However, those target
labels are useful for e.g. alert routing. With this commit, nothing
should change for vanilla job/instance target labels, but whoever has
more target labels can now still make use of them.

Signed-off-by: beorn7 <beorn@grafana.com>

* etcd-mixin: Parametrize instance labels to aggregate away

Signed-off-by: beorn7 <beorn@grafana.com>

2020-07-23 16:02:26 -07:00

mixin.libsonnet

Documentation/etcd-mixin: Reformulate alerting rules to use without rather than by (#12122 )

2020-07-23 16:02:26 -07:00

README.md

Documentation/etcd-mixin: Fix EtcdInsufficientMembers alerting

2018-10-15 19:23:43 +02:00

test.yaml

Documentation/etcd-mixin: Raise etcdHighNumberOfLeaderChanges threshold to 4

2020-06-25 15:38:15 -07:00

README.md

Prometheus Monitoring Mixin for etcd

NOTE: This project is alpha stage. Flags, configuration, behaviour and design may change significantly in following releases.

A set of customisable Prometheus alerts for etcd.

Instructions for use are the same as the kubernetes-mixin.

Background

For more information about monitoring mixins, see this design doc.

Testing alerts

Make sure to have jsonnet and gojsontoyaml installed.

First compile the mixin to a YAML file, which the promtool will read:

jsonnet -e '(import "mixin.libsonnet").prometheusAlerts' | gojsontoyaml > mixin.yaml

Then run the unit test:

promtool test rules test.yaml