rabbitmq monitoring: test exchange and queue

RESOLVED INCOMPLETE

Status

Developer Services
General
RESOLVED INCOMPLETE
6 years ago
3 years ago

People

(Reporter: dustin, Unassigned)

Tracking

Details

(Whiteboard: [good first bug][mentor=dustin@mozilla.com])

(Reporter)

Description

6 years ago
Beyond making sure that the process is running, we should test publishing a message to an exchange and seeing it come out in a queue on the other side.

I expect some checks exist to accomplish this already, so it just remains to find one and get it running.
(Reporter)

Comment 1

6 years ago
For a little background here, this bug is about doing some monitoring of a rabbitmq server.  We use nagios for monitoring, so that means that checks can be written in an arbitrary language, and just need to adhere to some simple guidelines for their output (one line of text, plus exit status).

This particular check would inject a message into rabbitmq, and then check that the message appears on an attached queue in a reasonable (configurable) amount of time.
(Reporter)

Updated

6 years ago
Whiteboard: [it starter bug]
(Reporter)

Updated

6 years ago
Whiteboard: [it starter bug] → [good first bug]
(Reporter)

Updated

6 years ago
Whiteboard: [good first bug] → [good first bug][mentor=dustin@mozilla.com]
(Reporter)

Comment 2

6 years ago
Since nagios is very much up in the air right now, I'm not going to work on this at the moment, which means it will probably get handed to the dev services group first.

I'm not totally convinced that this is necessary - let's see if there are failures that this would catch.
Assignee: dustin → server-ops-devservices
Component: Server Operations: RelEng → Server Operations: Developer Services
QA Contact: zandr → shyam
(In reply to Dustin J. Mitchell [:dustin] from comment #2)

> I'm not totally convinced that this is necessary - let's see if there are
> failures that this would catch.

+1 here. If we see failures, we can look at implementing this. Shelving for now.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.