Skip to content

chore: Remove integration-specific Python queue ops #19900

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
alexander-alderman-webb merged 1 commit into from
Oct 13, 2026
Merged

chore: Remove integration-specific Python queue ops #19900

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 0 additions & 3 deletions develop-docs/sdk/telemetry/traces/span-operations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -256,12 +256,9 @@ Messages/Queue spans are expected follow OpenTelemetry's [Messaging](https://git
| | topic.process | |
| queue | | |
| | queue.task | |
| | queue.task.celery | |
| | queue.task.rq | |
| | queue.task.delayed_job | |
| | queue.task.active_job | |
| | queue.submit | |
| | queue.submit.celery | |
| | queue.resque | |
| | queue.sidekiq | |
Comment on lines 257 to 266

@elramen elramen Oct 12, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This doesn't seem to align with conventions (task/submit vs publish/process). Is this a mistake or am I missing something?

@alexander-alderman-webb alexander-alderman-webb Oct 13, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

conventions are the source of truth.
not sure why it doesn't align.


Expand Down
Loading