Jaeger UI is not showing trace results for larger traces in RHOCP 4
Issue
-
While performing a query from the
Jaeger UI
forLarger traces
latency
and"502 - Bad Gateway"
error is observed. -
On performing a curl to the
Jaeger Route
as well a502 Bad Gateway
error is Shown :$ curl -vvvsSk 'https://jaeger-streaming-tracing-xxxxxxxxxxxxxxxxxxxx/api/traces?end=171xxxxxxxxxxx&limit=1&lookback=custom&maxDuration&minDuration&service=kafka-bridge-performance&start=17143xxxxxxxxxxx' -H 'Cookie: 476fbc14f3exxxxxxxxxx=71cdfc2f022016xxxxxxxxxxxxxxxx; _oauth_proxy=UDk5OTIwNDxxxxxxxxxxxxxx=|1714xxxxxxxxx|TTZxxxxxxxxxxx-xx=' < HTTP/1.1 502 Bad Gateway < gap-auth: P999204xx@cluster.local < gap-upstream-address: localhost:16686 < date: Mon, 29 Apr 2024 20:22:22 GMT < content-length: 0
Environment
-
Red Hat OpenShift Container Platform (RHOCP)
- 4
-
Red Hat OpenShift distributed tracing platform
- v1.53.0-4
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.