Title: Queue latency with Celery integration interpreted as milliseconds, whereas it's computed in seconds · Issue #4636 · getsentry/sentry-python · GitHub
Open Graph Title: Queue latency with Celery integration interpreted as milliseconds, whereas it's computed in seconds · Issue #4636 · getsentry/sentry-python
X Title: Queue latency with Celery integration interpreted as milliseconds, whereas it's computed in seconds · Issue #4636 · getsentry/sentry-python
Description: How do you use Sentry? Sentry Saas (sentry.io) Version 2.339 Steps to Reproduce Integrate a Celery queue via the Python SDK's Celery Integration Schedule tasks ending up in this queue Go to Insights -> Backend -> Queues Open average dura...
Open Graph Description: How do you use Sentry? Sentry Saas (sentry.io) Version 2.339 Steps to Reproduce Integrate a Celery queue via the Python SDK's Celery Integration Schedule tasks ending up in this queue Go to Insight...
X Description: How do you use Sentry? Sentry Saas (sentry.io) Version 2.339 Steps to Reproduce Integrate a Celery queue via the Python SDK's Celery Integration Schedule tasks ending up in this queue Go to Ins...
Opengraph URL: https://github.com/getsentry/sentry-python/issues/4636
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Queue latency with Celery integration interpreted as milliseconds, whereas it's computed in seconds","articleBody":"### How do you use Sentry?\n\nSentry Saas (sentry.io)\n\n### Version\n\n2.339\n\n### Steps to Reproduce\n\n1. Integrate a Celery queue via the Python SDK's Celery Integration\n2. Schedule tasks ending up in this queue\n3. Go to Insights -> Backend -> Queues\n4. Open average duration graph\n5. Look at average time in qeueue\n6. Observe values\n\n\n### Expected Result\n\nLatencies should match the actual time that tasks spent in the queue before being picked up by a worker \n\n### Actual Result\n\nGraph shows 1/1000 of the actual values (e.g. instead of displaying seconds, it's displaying milliseconds)\n\nDigging into the JSON raw data of relevant spans, the value messaging.message.receive.latency appears twice in the JSON (see attached screenshot), once without the milli unit and once with it. My hunch is that the unit is inserted erroneously downstream from the Celery integration, and picked up by the graph to show 'ms' on the y axis. The Celery integration definitely computes and writes the value in seconds (see second screenshot).\n\n\u003cimg width=\"1512\" height=\"910\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ae852cc4-fdb7-456e-aa7b-f2e2aa1f2caf\" />\n\u003cimg width=\"1509\" height=\"828\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/eb4682c2-c6d3-4081-85b2-eff5e2fdbb4b\" />","author":{"url":"https://github.com/ElstnerM","@type":"Person","name":"ElstnerM"},"datePublished":"2025-07-29T08:42:27Z","url":"https://github.com/getsentry/sentry-python/issues/4636"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:aa67ad41-99bd-49ff-c757-cb7bee02e421 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E6BE:7A49C:25EA6A:348824:6B0087F1 |
| html-safe-nonce | bfb9b614008f703bafe35da1eaacc76de60e9441f86ccce01aae2b8053cadf6c |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNkJFOjdBNDlDOjI1RUE2QTozNDg4MjQ6NkIwMDg3RjEiLCJ2aXNpdG9yX2lkIjoiMzgyMzkwMTkzNzY3NDI1ODQxNyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 1d5aeacb82addf0fe2eaaf2ef5566fd9b955513230d4fc4c4a7649e8fb1548bf |
| hovercard-subject-tag | issue:3272707508 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/getsentry/sentry-python/4636/issue_layout |
| twitter:image | https://opengraph.githubassets.com/429f1438f985c54e1826e15b9960692a7f8786231fda0b2d91dc389fc098bf8f/getsentry/sentry-python/issues/4636 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/429f1438f985c54e1826e15b9960692a7f8786231fda0b2d91dc389fc098bf8f/getsentry/sentry-python/issues/4636 |
| og:image:alt | How do you use Sentry? Sentry Saas (sentry.io) Version 2.339 Steps to Reproduce Integrate a Celery queue via the Python SDK's Celery Integration Schedule tasks ending up in this queue Go to Insight... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | ElstnerM |
| hostname | github.com |
| expected-hostname | github.com |
| None | 4d3d8e50f02c1d7bf86d5acfa1d3bfe9366abd6528a6b429eb07a168429d2b61 |
| turbo-cache-control | no-preview |
| go-import | github.com/getsentry/sentry-python git https://github.com/getsentry/sentry-python.git |
| octolytics-dimension-user_id | 1396951 |
| octolytics-dimension-user_login | getsentry |
| octolytics-dimension-repository_id | 137814779 |
| octolytics-dimension-repository_nwo | getsentry/sentry-python |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 137814779 |
| octolytics-dimension-repository_network_root_nwo | getsentry/sentry-python |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | db758f8e02b8257935fb03edf81a3e76eb3abd11 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width