Skip to content
This repository has been archived by the owner on Sep 7, 2019. It is now read-only.

How to extend for multiple queue monitoring? #31

Open
miguelHx opened this issue Jun 25, 2018 · 5 comments
Open

How to extend for multiple queue monitoring? #31

miguelHx opened this issue Jun 25, 2018 · 5 comments

Comments

@miguelHx
Copy link

miguelHx commented Jun 25, 2018

Hello, I am curious as to how we can extend to expose metrics for multiple queues.
Could you point me to where I can start?
I am kind of a newbie at this so any guidance would be appreciated.

@miguelHx miguelHx closed this as completed Jul 6, 2018
@zerok
Copy link
Owner

zerok commented Jul 7, 2018

Sorry, didn't have the time to look into your request :( Did you already solve it on your own?

@miguelHx
Copy link
Author

miguelHx commented Jul 8, 2018

I saw from issue #19 you mention that the queue name was there in the task class. I thought that maybe I should start there and work to get multiple queue monitoring. So that's why I closed the issue. Going to re-open, though. How can we extend for multiple queues?

@miguelHx miguelHx reopened this Jul 8, 2018
@zerok
Copy link
Owner

zerok commented Jul 9, 2018

I‘m currently afk, but I’d guess that the information about the queue is also included in the submitted event. You could then add the queue as additional label in the _incr*

I hope this helps 🙂

@miguelHx
Copy link
Author

miguelHx commented Jul 9, 2018

I'll look into that, thanks!

@javabrett
Copy link
Contributor

I think this can be done by capturing and saving the task-sent event:

task-sent(uuid, name, args, kwargs, retries, eta,expires, queue, exchange, routing_key, root_id,parent_id)

... which can then be used to lookup queue, exchange and routing_key if desired, by uuid, then later discarded.

Anyone looked at that yet? Bit of work there to adapt current code, thinking not done yet ...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants