If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add nagios check for gaia_bumper.stamp

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
4 years ago
3 years ago

People

(Reporter: catlee, Assigned: ashish)

Tracking

(Blocks: 1 bug)

Details

(Reporter)

Description

4 years ago
After the gaia bumper runs, it touches /builds/gaia_bumper/gaia_bumper.stamp.

Can we add a nagios check for buildbot-master66.srv.releng.usw2.mozilla.com that this file isn't too old?

The bumper is set to run every 5 minutes right now, so make nagios alert after 15?
Assignee: server-ops-releng → server-ops
Component: Server Operations: RelEng → Server Operations
QA Contact: arich → shyam
Blocks: 885560
(Assignee)

Updated

4 years ago
Assignee: server-ops → ashish
(Assignee)

Comment 1

4 years ago
I'm set to add this check but it requires the "file_age" NRPE plugin to be realised on the server. The default check_file_age has a different set of parameters. Thanks!

:arr For reference, check_file_age_ok_not_exists is the check_command I'm considering (and that file_age provides via NRPE)
Flags: needinfo?(arich)
(Assignee)

Updated

4 years ago
Status: NEW → ASSIGNED
I refer you back to catlee for making any changes to AWS systems.
Flags: needinfo?(arich) → needinfo?(catlee)
(Reporter)

Comment 3

4 years ago
nrpe on this machine is managed by puppet. do we have a recipe for getting the "file_age" nrpe plugin deployed with puppet?
Flags: needinfo?(catlee)
(Assignee)

Comment 4

4 years ago
Co-ordinated with :catlee on IRC and worked this out. Check has been added:

https://nagios.mozilla.org/releng-scl3/cgi-bin/extinfo.cgi?type=2&host=buildbot-master66.srv.releng.usw2.mozilla.com&service=File+Age+-+%2Fbuilds%2Fgaia_bumper%2Fgaia_bumper.stamp

Please reopen this bug if there are any false alerts. Thanks!
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.