-
Notifications
You must be signed in to change notification settings - Fork 12
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
Jaeger DEV: Integrate with ES #1481
Comments
ES service cannot be found by Jaeger-Operator spawned pods. Istio sidecarts injected into them successfully. Support ticket to CNS created: |
After correctly configuring the ES service thanks to Will, we ran into an issue where the After doing some research, it seems that the latest release of Jaeger (1.41) does not yet support ES v8.x+. There is a long-run issue open in the Jaeger repository for this. For reference, our ElasticSearch instance is currently at v8.5.0 According to ES, it should be possible to integrate https://www.elastic.co/guide/en/apm/guide/current/jaeger-integration.html |
Closing this issue as Jaeger successfully connects to the ES instance and that is the normal scope. Continuing work on the last comment in #1505 |
From #1462 (comment)
When trying to start up a Jaeger instance some of the created pods crash out complaining about Elastic.
Example in
simple-prod-collector
(same error insimple-prod-query
)Of note is that Souheil was able to remove the ES configuration and have it run in memory to just check things out and it worked fine.
The text was updated successfully, but these errors were encountered: