Open fmassot opened 5 months ago
Awesome! thanks @liuxuzxx!
let's add this to the documentation.
FYI, you don't need the jaeger-query deployment if you use Grafana and the Jaeger plugin.
Awesome! thanks @liuxuzxx!
let's add this to the documentation.
FYI, you don't need the jaeger-query deployment if you use Grafana and the Jaeger plugin.
Okay, thank you, I will try use Grafana and the Jaeger plugin
FYI, you don't need the jaeger-query deployment if you use Grafana and the Jaeger plugin.
@fmassot
But in that case you need to have rewrite path proxy in between. As Grafan plugin do not support path prefix.
At least I wasn't able to make it working. With a simple envoy proxy between them everything working fine.
quickwit: v0.8.2
Deployment mode: helm
jaeger-query: v1.60.0
Jaeger's official documentation does not give the deployment method of jaeger-query. CRD resources given to Jaeger-operator: Jaeger’s three deployment methods: allInOne, production, streaming.
Therefore, an example of jaeger-query deployment needs to be given.
The following is the yaml of my Deployment for deploying jaeger-query
If you are using version 1.60.0 of jaeger, you need to modify the environment variables
When quickwit is deployed in distributed form using helm, the environment variables : GRPC_STORAGE_SERVER
The document gives the configuration when deploying in allInOne mode, but does not give how to configure it when helm is deployed, and many services have the 7281 port exposed, making it difficult to tell which one to use.