Skip to content

Elasticsearch

Auto-Discovery
Health Check
Metrics
Logs

Agent uses a HTTP check if the service listen on port 9200.

If some auto-detected parameters are wrong, you can manually override them by adding the following to /etc/glouton/conf.d/99-local.conf:

service:
[...]
# For an Elasticsearch running outside a container
- type: "elasticsearch"
address: "127.0.0.1"
port: 9200
# For an additional Elasticsearch running outside a container
- type: "elasticsearch"
instance: "NAME_ASSOCIATED_WITH_YOUR_ADDITIONAL_SERVICE"
address: "127.0.0.1"
port: 9201
# For an Elasticsearch running in a Docker container
- type: "elasticsearch"
instance: "CONTAINER_NAME"
address: "172.17.0.2"
port: 9200

Agent gathers the following metrics:

MetricDescription
service_statusStatus of Elasticsearch
elasticsearch_docs_countNumber of documents stored in all indices
elasticsearch_jvm_gcNumber of garbage collection per second
elasticsearch_jvm_gc_utilizationGarbage collection utilization in percent
elasticsearch_jvm_heap_usedHeap memory used in bytes
elasticsearch_jvm_non_heap_usedNon-Heap memory used in bytes
elasticsearch_sizeSize of all indices in bytes
elasticsearch_searchNumber of search in a shard per seconds
elasticsearch_search_timeAverage time took by search in secondss
elasticsearch_cluster_docs_countNumber of documents stored in all indices of the cluster
elasticsearch_cluster_sizeSize of all indices of the cluster in bytes