resultsdb01.qa has a fedora-messaging listener that has its own queue.
Monitoring how that queue is doing in nagios would alert of misbehave on the consumer (such as the one we had this week-end due to a message without body).
Is this in it's own rabbitmq instance? or in the main one?
@abompard has done some rabbit monitoring work...
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
It is in the main one
Metadata Update from @mizdebsk: - Issue tagged with: easyfix, monitoring
I imagine https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=ee4a746691a0cb6edd81505a275ce82a33a40542 fixes this (sans any threshold adjustments)?
That would alert if it got too large, but wouldn't alert if there were no messages coming in from it.
We need something like the checks we have that use datanommer to query for the last message from that service.
https://apps.fedoraproject.org/datagrepper/raw?category=resultsdb
There's some nagios checks for other services like that.
Sorry if I sound like a broken record, but what does https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=93d0eeaf54ff57fea9c8942f25618c826b454c54 achieve, then?
oh man, you are in fact right. I somehow was looking at another commit or something. ;(
My bad... you are right, this does what we want. :)
Sorry about that.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Those are indeed two different commits. Sorry if my link-fu confused you. :p
Log in to comment on this ticket.