etcd/Documentation
Sam Batschelet 9915d02022 *: Change gRPC proxy to expose etcd server endpoint /metrics
This PR resolves an issue where the `/metrics` endpoints exposed by the proxy were not returning metrics of the etcd members servers but of the proxy itself.

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
2019-04-10 16:09:32 -04:00
..
benchmarks documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
dev-guide documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
dev-internal documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
etcd-mixin etcd-mixin: Improve etcdHighNumberOfLeaderChanges,etcdHighNumberOfFailedProposals message 2019-02-04 09:28:23 +02:00
learning documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
op-guide *: Change gRPC proxy to expose etcd server endpoint /metrics 2019-04-10 16:09:32 -04:00
platforms documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
rfc documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
upgrades documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
v2 documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
README.md documentation: display docs.md in github browser 2017-01-11 10:37:42 -08:00
branch_management.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
demo.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
dl_build.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
docs.md Documentation/*: change github url, import path from coreos to etcd-io 2018-09-12 22:05:08 +05:30
faq.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
integrations.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
metrics.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
production-users.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
reporting_bugs.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00
tuning.md documentation: initial metadata additions for website generation (#10596) 2019-04-01 13:57:24 -07:00

README.md

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.

Getting started

New etcd users and developers should get started by downloading and building etcd. After getting etcd, follow this quick demo to see the basics of creating and working with an etcd cluster.

Developing with etcd

The easiest way to get started using etcd as a distributed key-value store is to set up a local cluster.

Operating etcd clusters

Administrators who need a fault-tolerant etcd cluster for either development or production should begin with a cluster on multiple machines.

Setting up etcd

System configuration

Platform guides

Security

Maintenance and troubleshooting

Learning

To learn more about the concepts and internals behind etcd, read the following pages: