Skip to content
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

Tempo: Streaming search does not pass X-Scope-OrgID header #81998

Closed
thomaspurchas opened this issue Feb 6, 2024 · 3 comments
Closed

Tempo: Streaming search does not pass X-Scope-OrgID header #81998

thomaspurchas opened this issue Feb 6, 2024 · 3 comments
Labels
area/search datasource/Tempo triage/needs-confirmation used for OSS triage rotation - reported issue needs to be reproduced

Comments

@thomaspurchas
Copy link

thomaspurchas commented Feb 6, 2024

What happened?

Trying to perform trace searches using Grafana with a Tempo datasource, with both multi-tenancy and streaming searches turned on. Result is a query error say no org id.

image

What did you expect to happen?

Streaming searches to work.

Did this work before?

Streaming searches worked before turning on Multi tenancy in Tempo. Disabling streaming searches or Multi tenancy fixes search errors.

How do we reproduce it?

  1. Install Grafana 10.3 and latest Tempo
  2. Turn on traceQLStreaming feature toggle
  3. Turn on Multitenancy in Tempo
  4. Connect Grafana to Temp, and add x-scope-orgid header in Tempo datasource
  5. Try to perform a trace Search (not a traceID lookup)
  6. Notice that no org id error is returned.

Is the bug inside a dashboard panel?

No response

Environment (with versions)?

Grafana: 10.3
OS: Mac OS
Browser: Chrome and Safari

Grafana platform?

Kubernetes

Datasource(s)?

Tempo

@williamfeng323
Copy link

I also encounter this issue. The custom header does not work at all. Grafana version 9.5.2

@usmangt usmangt added area/search datasource/Tempo triage/needs-confirmation used for OSS triage rotation - reported issue needs to be reproduced labels Feb 22, 2024
@joey-grafana
Copy link
Contributor

Hello, this should be fixed 10.4. If you run into any issues in 10.4 please let us know.

@thomaspurchas
Copy link
Author

For those wondering, this appears the PR that fixes this issue #81693

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/search datasource/Tempo triage/needs-confirmation used for OSS triage rotation - reported issue needs to be reproduced
Projects
Status: Done
Development

No branches or pull requests

4 participants