Skip to content

Clarify double instrumentation issue #13751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 23, 2025
+2 −0
Merged

Clarify double instrumentation issue #13751

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e64d2e0
Clarify double instrumentation issue
antonpirker May 19, 2025
6a31021
typo
antonpirker May 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/platforms/python/integrations/celery/crons.mdx
View file
Original file line number Diff line number Diff line change
@@ -42,6 +42,8 @@ Next, initialize Sentry. Where to do this depends on how you run beat:

Make sure to also set `monitor_beat_tasks=True` in `CeleryIntegration`.

If you have set `monitor_beat_tasks=True` make sure that you do not do manual task monitoring using the `@sentry_sdk.monitor` decorator, because this will lead to double instrumentation.

In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/).

Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.