fix(otel): flush telemetry on shutdown with fresh context (DEV-33)#5
Merged
Merged
Conversation
- Use a fresh 10s context for tracer and metrics shutdown - Stop passing the cancelled serverCtx, which aborted the flush - Pass serverCtx directly to init; drop redundant alias vars
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
1 participant
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.
Closes DEV-33.
OTel tracer/metrics shutdown reused the already-cancelled
serverCtx, so the export flush deadline was expired on every graceful shutdown — buffered spans/metrics dropped.Fix
context.Background()timeout for each shutdown, mirroringsrv.StopserverCtxdirectly to init; drop the redundant alias vars🤖 Generated with Claude Code