Β© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Ensuring Trace Continuity Between Client and Server with OpenTelemetry - Effect Community
EC
Effect Community
β’
9mo ago
β’
8 replies
Kishore
Ensuring Trace Continuity Between Client and Server with OpenTelemetry
Hello team
So I am using http platform to define client and server
. Everything is working perfect
One thing I observed is
: When the httpClient is making a request to server
, its sending
Traceparent
Traceparent
header to the server that also contains the trace and spanid
.
On the server though
, its showing as a missing span
, probably because this span is associated on client
.
How can I make sure the whole trace is present on server as well
? Since I use otel on server and not on web for observability
.
Please suggest what the best way forward here is
.
Thanks
.
Effect Community
Join
Production-grade applications in TypeScript.
6,221
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Similar Threads
Was this page helpful?
Yes
No
Recent Announcements
Similar Threads
Propagating trace context between a backend and frontend typically involves ensuring that trace i...
EC
Effect Community / opentelemetry
2mo ago
Seeking OpenTelemetry Service Recommendations for Client and Server Use
EC
Effect Community / opentelemetry
3mo ago
Ensuring `forceFlush` Before `shutdown` in `@effect/opentelemetry` Metrics
EC
Effect Community / opentelemetry
2y ago
Default Loading of Optional `@opentelemetry/sdk-trace-web` in `@effect/opentelemetry` Package
EC
Effect Community / opentelemetry
3y ago