-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
Monitoring of queues and task results #297
Comments
I'll try to get started on a proof of concept this week or next, our need for queue and task result monitoring became a bit more urgent than first anticipated. |
I see you're working on pydantic 2.0 which is exciting, @samuelcolvin, so don't take this as a bump (I also didn't get to work on this in early April as I intended!) I have some time this Sunday, so before I start I thought I'd ask if you have any thoughts about timeframe for rewrite (if you still intend to?). If it's right around the corner I'll probably not write any redis integration yet, only focus on setting up the stack etc. |
I don't think I'm going to have much time to devote to this for a while. Pydantic v1.9.1 and then V2 are the priorities when I get to work on OS. Thanks for being understanding. |
Good luck! 😊 Excited to try it out. |
While Pedantic is working on something interesting, I can offer to test my dashboard for arq. I would welcome any feedback. |
Hi!
I'm creating this issue to ask about monitoring of queues and task results. It was suggested in another issue that you'd like to have this as its own project. I am in need of a monitoring tool for our tasks, and I'd be up to start a proof of concept using FastAPI (even though my redis skills isn't the best)
In #277 you're suggesting a rewrite of
arq
. Could you, if you already know, talk a bit about whether you think the new implementation would affect such a monitoring tool? Will sorted lists (andzadd
,zrange
?) still be used?There's not really a big rush for me to have this, so if you don't know yet, that's okay. 😊
The text was updated successfully, but these errors were encountered: