ElasticSearch Exporter with own service discovery
Its SD does not depend on Prometheus SD. You only set the exporter address in prometheus config as a target,
then Exporter starts getting metric.
Get list of services names from consul
get service properties from consul
filter with tag specified in cli parameters
get parameters from the KV. Parameters' path are designed to be /kv/monitoring/service_name/tag
Only one service's monitoring agent instead of N agents for N services
Live service discovery w/o restarting/reloading
Metrics are exported in background and stored in the cache. So it prevents high resources utilization.