Skip to content

docs: add note about Tempo appProtocol in proxy-trace.md #5963

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.

Sign up for GitHub

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

Open
rtomadpg wants to merge 3 commits into
base: main
Choose a base branch
from
+12 −0
Open

docs: add note about Tempo appProtocol in proxy-trace.md #5963

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2570ffc
docs: add note about Tempo appProtocol in proxy-trace.md
rtomadpg May 8, 2025
1927037
Update proxy-trace.md
rtomadpg May 8, 2025
8afd879
Merge branch 'main' into patch-1
jukie Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions site/content/en/latest/tasks/observability/proxy-trace.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -347,6 +347,18 @@ spec:
EOF
```

### Tempo and appProtocol

When using Grafana Tempo it is important to note that the [tempo-distributed Helm chart](https://github.com/grafana/helm-charts/tree/main/charts/tempo-distributed)
will omit a `appProtocol` in the `tempo-distributor` Service. Without this protocol hint, Envoy will send traces to Tempo using the wrong protocol: HTTP, instead of GRPC.

You can add the protocol hint to the `tempo-distributor` Service, by supplying these values to the "tempo-distributed" Helm chart:

```yaml
distributor:
appProtocol:
grpc: grpc

@arkodg arkodg May 8, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

instead of grpc in the key, can we use kubernetes.io/h2c instead ?
this is what upstream would ideally like
https://gateway-api.sigs.k8s.io/guides/backend-protocol/

=======
### Sampler

For OpenTelemetry tracing, you can configure the sampler using the `openTelemetry.sampler` field.
Expand Down
Loading