Closed
Bug 914218
Opened 12 years ago
Closed 10 years ago
Monitor successful completion of Postgres base backup and pg_dump backups
Categories
(Data & BI Services Team :: DB: MySQL, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: selenamarie, Assigned: mpressman)
References
Details
(Whiteboard: [2014q2] June [data: monitoring])
We need a monitor that checks for successful completion of a Postgres base backup and pg_dump backups, in particular for Socorro.
We do this for mysql as indicated in bug 811013, and we should have the same for postgres!
Updated•11 years ago
|
Whiteboard: [2014q1]
Updated•11 years ago
|
Whiteboard: [2014q1] → [2014q2] April
Updated•11 years ago
|
Assignee: server-ops-database → mpressman
Updated•11 years ago
|
Whiteboard: [2014q2] April → [2014q2] May
Updated•11 years ago
|
Whiteboard: [2014q2] May → [2014q2] June
Assignee | ||
Comment 1•11 years ago
|
||
nagios check Committed in revision 89748
Assignee | ||
Comment 2•11 years ago
|
||
This is completed
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 3•11 years ago
|
||
https://nagios.mozilla.org/phx1/cgi-bin/extinfo.cgi?type=2&host=backup4.db.phx1.mozilla.com&service=Check+Breakpad+Backups
shows that the status "OK" but the output is "NRPE: Unable to read output"
This should be a warning status! Also, the script should be fixed so that the output is readable.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Updated•11 years ago
|
Whiteboard: [2014q2] June → [2014q2] June -[monitoring]
Updated•11 years ago
|
Whiteboard: [2014q2] June -[monitoring] → [2014q2] June [data: monitoring]
Updated•11 years ago
|
Product: mozilla.org → Data & BI Services Team
Comment 4•10 years ago
|
||
The script was fixed because it's now green and says "Backups OK: nothing too old."
I put some logic into the script to be unknown if it's not critical, warning or OK (as opposed to OK if not crit or warn).
Status: REOPENED → RESOLVED
Closed: 11 years ago → 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•