You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using a Google Cloud HTTP load balancer in front of our Elastic Search cluster, Jaeger Query component is unable to search for traces.
To Reproduce
Steps to reproduce the behavior:
Deploy an elasticsearch cluster in Google Cloud
Deploy a load balancer in front of the cluster with an HTTPS route
Configure jaeger-query to use the elasticsearch cluster
Search for traces
Expected behavior
I should be able to search for traces
Screenshots
After intercepting HTTP traffic between jaeger-query and elasticsearch, this is the query blocked by the load balancer with a 400 error:
Additional context
Google Cloud Load balancer does not support body in HTTP GET queries and blocks it. The ElasticSearch client should be able to make queries with POST instead of GET (maybe if a flag is activated). Meanwhile, we're using TCP load balancer but it's not a best practice. https://cloud.google.com/load-balancing/docs/https#illegal_request_and_response_handling
The text was updated successfully, but these errors were encountered:
Yeah ! Currently working on a PR, just having trouble to setup my go environment on Windows :)
There's a SendGetBodyAs on the es client, I was thinking adding a cli flag such as --es.send-get-body-as="POST"
Describe the bug
When using a Google Cloud HTTP load balancer in front of our Elastic Search cluster, Jaeger Query component is unable to search for traces.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should be able to search for traces
Screenshots
After intercepting HTTP traffic between jaeger-query and elasticsearch, this is the query blocked by the load balancer with a 400 error:
Version:
Additional context
Google Cloud Load balancer does not support body in HTTP GET queries and blocks it. The ElasticSearch client should be able to make queries with POST instead of GET (maybe if a flag is activated). Meanwhile, we're using TCP load balancer but it's not a best practice.
https://cloud.google.com/load-balancing/docs/https#illegal_request_and_response_handling
The text was updated successfully, but these errors were encountered: