-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Export queue stats on the metrics endpoint #1173
Comments
Minor addition to this - it's very useful to monitor how old is the oldest message in queue. We'd like to monitor queue health based on that as well. Would be great to add it if someone takes this up. |
Implements mher#1173 * Quick fix synchronous redis calls. Redis broker calls were synchronous, so blocking the main thread. This moves them to ThreadPoolExecutor * Update workers list regularly for up-to-date metrics Previously self.workers was only updated only on UI events. This is no longer fine as we use the data to produce up-to-date metrics
Implements mher#1173 * Quick fix synchronous redis calls. Redis broker calls were synchronous, so blocking the main thread. This moves them to ThreadPoolExecutor * Update workers list regularly for up-to-date metrics Previously self.workers was only updated only on UI events. This is no longer fine as we use the data to produce up-to-date metrics
Bump. Meanwhile, just sharing a simple go scraper to record the Broker's tab queue stats. Then run |
I’d like to autoscale my Celery workers (running in Kubernetes) based on the queue “length”; e.g. if there are many tasks scheduled in queue A, i’d boot up a few more workers for that queue.
I’d imagine either a queue length
and/or the queue name exposed in
flower_events_total
:The text was updated successfully, but these errors were encountered: