Fix logfire "Found propagated tracing"#36
Merged
Conversation
The logfire dashboard was warning us: 'Found propagated trace context'. This change solves this problem. Check https://pydantic.dev/docs/logfire/instrument/distributed-tracing/#unintentional-distributed-tracing.
thigcampos
approved these changes
Jun 21, 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.
Merge first
Summary
After deploy donotcommit to FastAPI cloud and setting up the logfire token, we started getting the warning "Found propagated trace context".
Fix
The logfire docs suggested setting the
distributed_tracingto False.Rationale
Read this whole page to understand the problem further, but I believe this has to do with both FastAPI Cloud and Logfire observing the same app.