-
Notifications
You must be signed in to change notification settings - Fork 41
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
Dashboard for PQ #68
Comments
Hi Tom. Looks great – how about a screenshot? You can just drag any PNG into a Markdown field on Github and it'll upload an image. For who's listening, that's a tricky one because even if there was a way to query that in PostgreSQL it would probably require superuser permission. |
@malthe thanks for the tip - here's a screenshot: Re. who's listening - cheers, you've saved me time trying to find a workaround. I think more heavyweight solutions are possible but not really in keeping with the unopinionated spirit of |
@MisterKeefe I suppose we could send a notification the other way – as a sort of health probe – such that every N seconds, each worker would send a notification that it's listening and the dashboard could pick that up if it subscribed to them using its own listener. But at some point, you're probably better off using a proper monitoring system, e.g. https://prometheus.io/. |
Hi,
This is not an issue with PQ itself, please close if not of interest!
I've recently created a dashboard for
pq
, imaginatively namedpq-dashboard
. The intention was to create something generic likerq-dashboard
, which people use withrq
. It's available viapip install pq-dashboard
as you would expect. It supports inspecting queues and items, searching / deleting / requeueing items, and understands how the task API works.I'm raising this issue just to bring the dashboard to your attention and in case you have any advice for further development / feature suggestions. Something I'd like to do (which
rq-dashboard
has) is expose which worker processes are processing queue items - but this might be hard to do generically since AFAIKpostgres
doesn't provide an easy way of seeing who's listening topq_notify
.Thanks,
Tom
The text was updated successfully, but these errors were encountered: