-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exporter for Elasticsearch #1630
Comments
cc @alolita |
We will be happy to soon propose a first small PR according to the Contributing guidelines. |
Consider this to be in the contrib repo, I will move the issue as well. |
There is already an Elastic exporter for traces and metrics: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/master/exporter/elasticexporter |
Thanks for the guidance @tigrannajaryan and @bogdandrutu . I'll close this issue and we will ship logs to Elasticsearch through the OpenTelemetry Collector exporter for Elastic. |
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
Is your feature request related to a problem? Please describe.
The problem is to export OpenTelemetry data, primarily logs, to Elasticsearch the same way many observability collectors can send data to Elasticsearch.
Describe the solution you'd like
The solution would be an OpenTelemetry Collector Exporter for 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.
Elasticsearch 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. 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.
Examples of observability collectors supporting exports to Elasticsearch:
Describe alternatives you've considered
An alternative would be to have Elasticsearch being capable of ingesting the OTLP protocol. 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.
Additional context
Elasticsearch is published under the Apache Software License 2.
The text was updated successfully, but these errors were encountered: