[ZBXNEXT-1695] Make "database is down" alert subject to Maintenance Period Created: 2013 Apr 02  Updated: 2013 Apr 04

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Server (S)
Affects Version/s: 2.0.5
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Stephen Davies Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: database, dbwatchdog, maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

All


 Description   

The "Zabbix database is down" alert currently does not take Maintenance periods into account.

I got this notification every day because the database was down for backup - in a defined maintenance period.

The only current option is to disable the alert. It should be possible to disable it only for the maintenance period.

 Comments   
Comment by Oleg Ivanivskyi [ 2013 Apr 03 ]

From documentation:

Availability of Zabbix server depends on availability of back-end database. It cannot work without a database. Database watchdog, a special Zabbix server process, will alarm Zabbix administrators in case of disaster. The watchdog will send notifications to the user group set here if the database is down. Zabbix server will not stop; it will wait until the database is back again to continue processing.

I think that in this situation, it would be more correct to stop Zabbix server rather than put maintenance mode.
How do you imagine the work Zabbix server without a database?

Comment by Stephen Davies [ 2013 Apr 04 ]

Stopping the server is certainly an option but the definition of maintenance periods already includes the "no data collection" option - which I assume turns off database updates.

If no updating is being done, Zabbix should be able to work without a database for a while.

Also, if Zabbix "will wait until the database is back again to continue processing", a mechanism to prevent sending the "database down" notification still seems worthwhile.

Cheers,
Stephen

Generated at Tue Apr 16 20:45:18 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.