Skip to content

Conversation

dhruv-ahuja
Copy link
Contributor

Creates a dedicated section in the Celery documentation covering the distributed tracing scenario, as discussed in #972.

Copy link

codecov bot commented Oct 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!



if __name__ == "__main__": # (2)!
logfire.configure(service_name="client-app")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
logfire.configure(service_name="client-app")
logfire.configure(service_name="client")

Then this can fit in a screenshot nicely, which should be added

add.delay(42, 50)
```

1. Mark the configuration as running in a distributed tracing environment. This is only required for the worker.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Explain in more detail and link to docs.

1. Mark the configuration as running in a distributed tracing environment. This is only required for the worker.
2. Running the file directly will simulate a client application that calls the Celery task.

The keyword arguments of [`logfire.instrument_celery()`][logfire.Logfire.instrument_celery] are passed to the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this to before the installation, it doesn't fit here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants