-
Notifications
You must be signed in to change notification settings - Fork 28
Core services healthchecks
Nicolas Degory edited this page Jul 15, 2017
·
11 revisions
This page lists the checks that should be run to validate the deployment of the core services
order | service | depends on | context | test | command |
---|---|---|---|---|---|
1 | elasticsearch | single mode | cluster health should be yellow | curl -sf elasticsearch:9200/_cluster/health?wait_for_status=yellow&timeout=15s | |
1 | cluster mode | cluster health should be green | curl -sf elasticsearch:9200/_cluster/health?wait_for_status=green&timeout=30s | ||
2 | etcd | * | endpoint health | etcdctl --endpoints "http://etcd:2379" endpoint health | grep -qw healthy | |
3 | nats | * | api availability | curl -sf "nats:8222/subsz" | |
4 | ampbeat | nats, elasticsearch | docker service logs amp_ampbeat 2>&1 | grep -q "INFO ampbeat is running" | |
5 | kibana | elastisearch, ampbeat | UI availability | curl -sf "kibana:5601/app/kibana#/discover" | |
6 | prometheus | ||||
7 | alertmanager | prometheus | |||
8 | node_exporter | prometheus | |||
9 | nats_exporter | nats, prometheus | |||
10 | haproxy_exporter | haproxy, prometheus | |||
11 | grafana | ||||
12 | proxy | ||||
13 | amplifier | nats, elasticsearch, etcd | |||
14 | gateway | amplifier | |||
15 | agent | nats | |||
16 | portal | gateway |