© 2026 Hedgehog Software, LLC
Twitter
GitHub
Discord
System
Light
Dark
More
Communities
Docs
About
Terms
Privacy
Search
Star
Feedback
Setup for Free
Issue with parent span not being passed to forked fiber - Effect Community
EC
Effect Community
•
3y ago
•
7 replies
imagio
Issue with parent span not being passed to forked fiber
I
've dug in more with Tracer and Sentry
, almost have things working really nicely
. One issue is that when I
forkDaemon
forkDaemon
the forked fiber doesn
't get its parent span
. That makes sense in a lot of cases
, but in others I do want to
forkDaemon
forkDaemon
and keep the parent span
. How might I do that
?
Effect Community
Join
Production-grade applications in TypeScript.
6,221
Members
View on Discord
Resources
ModelContextProtocol
ModelContextProtocol
MCP Server
Recent Announcements
Similar Threads
Was this page helpful?
Yes
No
Similar Threads
Inclusion of Fiber ID in Span Attributes
EC
Effect Community / opentelemetry
3y ago
Investigating the Source of a Parent Span in HttpRouter with No W3C Trace Headers
EC
Effect Community / opentelemetry
8mo ago
Modifying Span Names in HttpApi with Middleware
EC
Effect Community / opentelemetry
14mo ago
Issue with `traceFlags` Not Being Set When Value is 0 in `Tracer.withSpanContext`
EC
Effect Community / opentelemetry
7mo ago