feat(effect): Derive span ops for Effect tracer spans - #23215
Merged
Conversation
Effect spans are named by user code, so the tracer already derives the origin from the span name. The op now follows the same signal: `@effect/platform` names its HTTP spans `http.server`/`http.client`, which map onto the matching ops, and everything else is arbitrary user work that falls back to `function`. A blanket `function` op was rejected because it would bury Effect's platform HTTP spans under a generic category. Ref JS-3318 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
size-limit report 📦
|
msonnb
marked this pull request as ready for review
August 10, 2026 09:49
msonnb
requested review from
mydea,
nicohrubec and
s1gr1d
and removed request for
a team
August 10, 2026 09:49
nicohrubec
approved these changes
Aug 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Effect spans are named by user code, the tracer already derives the origin from the span name. The op now follows the same signal:
@effect/platformnames its HTTP spanshttp.server/http.client, which map onto the matching ops, and everything else is arbitrary user work that falls back tofunction.part of #23138