![]() * 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> |
||
---|---|---|
.. | ||
benchmarks | ||
dev-guide | ||
dev-internal | ||
etcd-mixin | ||
learning | ||
metrics | ||
op-guide | ||
platforms | ||
rfc | ||
triage | ||
upgrades | ||
README.md | ||
_index.md | ||
branch-management.md | ||
demo.md | ||
dl-build.md | ||
faq.md | ||
integrations.md | ||
metrics.md | ||
reporting-bugs.md | ||
tuning.md |
README.md
The etcd documentation
etcd is a distributed key-value store designed to reliably and quickly preserve and provide access to critical data. It enables reliable distributed coordination through distributed locking, leader elections, and write barriers. An etcd cluster is intended for high availability and permanent data storage and retrieval.
Please note that the files in this directory are source files for the built and rendered documentation that can be viewed at etcd.io/docs.