![]() ![]() I cannot configure the listening port (is not a problem because i can use push gateway…). Was installed like a plugin on Opensearch. ![]() Volume of metrics (with full options) : 60 000 * 2 elasticsearch exporter (like 2 for HA) Ok it is a spof, but I just have to install it on another machine to have HA. With just one install of this exporter, i have all metrics of cluster and nodes ! (If i install elasticsearch exporter on another node, we will have 22 000 * 2 metrics scraped.)įor information, we all options set, elasticsearch exporter generate 60 000 metrics by default. ![]() With es.all this exporter generated 22 000 metrics AND i have all metrics for all nodes ! I use es.all option to retrieve all cluster and node stats. Was installed like a java process on one physcal machine Opensearch. The OpenSearch exporter works the same way as the original Elasticsearch exporter. Even for Elasticsearch exporter the recommendation was to install it on all nodes (because generally the assumption is that Prometheus is scraping metrics from all cluster nodes thus the plugin must be present on every node). I would be really interested in learning more details. If i want monitoring cluster, i need to deploy this plugin on all nodes ? > Installed prometheus-exporter with folder name prometheus-exporter * suppressAccessChecksįor descriptions of what these permissions allow and the associated risks. * Classname: .PrometheusExporterPluginįolder WARNING: plugin requires additional permissions Retrieving zip from file:///home/osadmin/prometheus-exporter-1.2.3.zipĭescription: Export OpenSearch metrics to Prometheus > Downloading file:///home/osadmin/prometheus-exporter-1.2.3.zip It's a scenario we are also looking at in parallel but the adoption path of OpenTelemetry collectors for existing Elasticsearch users would be steeper.Įlasticsearch is published under the Apache Software License 2.So, it seems good now : -> Installing file:///home/osadmin/prometheus-exporter-1.2.3.zip Fluent Bit: Fluent Bit Elasticsearch OutputĪn alternative would be to have Elasticsearch being capable of ingesting the OTLP protocol.This is the rationale to propose to add the Elasticsearch exporter directly in the opentelemetry-collector repository, next to the Prometheus, Zipkin and Jaeger exporters.Įxamples of observability collectors supporting exports to Elasticsearch: This exporter should try to support 6.8+ versions of Elasticsearch as well as the recent ones (7.x) to help Elasticsearch users interested in adopting OpenTelemetry collectors.Įlasticsearch is a very popular Open Source storage for logs in a similar way Prometheus is very popular for metrics and Jaeger or Zipkin are popular for traces. The solution would be an OpenTelemetry Collector Exporter for Elasticsearch. The problem is to export OpenTelemetry data, primarily logs, to Elasticsearch the same way many observability collectors can send data to Elasticsearch. Is your feature request related to a problem? Please describe. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |