-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Feature]: Support elasticsearch data stream #4708
Comments
Is this because the client library used for connecting to Elasticsearch is outdated? Namely, I see in the logs of version 1.54 of the collector that the client is olivere/[email protected]. This client is from July 27th, 2021. The client is also not being updated anymore, it would appear. Namely, it was last updated to version 7.0.32 on Mar 19th, 2022. This is almost two years ago now. Elastic has its own go library now: https://github.com/elastic/go-elasticsearch. |
I see that the OpenSearch project has the same feature-request. |
I am currently working on this feature, but I prefer to implement it in jaeger v2 |
@JaredTan95 +2 for v2, but what specifically is the difference? Our storage implementations are currently identical in v1 and v2 (with the exception of configuration) |
Currently, if we want to use esILM policy, we need to create aliases and we need to create the |
|
Requirement
https://www.elastic.co/guide/en/elasticsearch/reference/current/data-streams.html
Problem
I has created a data stream index template, and I tried
--es.use-aliases=true
but not work.Proposal
No response
Open questions
No response
The text was updated successfully, but these errors were encountered: