Please also provide the Zabbix servername that is reporting this issue - so that those who may receive this message, but are not aware exactly which server Zabbix is running on, can quickly find out which server to look at and fix.

Initial draft of the specification is available at http://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-970

just a note - ZBX-6305 will add possibility to specify email of sender in format "Name <email>" (of course specifying just email like before works too).

This should help for cases mentioned by P Sorensen above.

note that "server name" we can see in the upper right corner can not be obtained by the server, as it is only in the frontend config file

richlv i guess that the server could send its hostname or ip address at least.

Telling what error is it, more details on database (address/database) would be ideal as well.

(1) Documentation
It would worth to add more technical details to documentation https://www.zabbix.com/documentation/2.4/manual/web_interface/frontend_sections/administration/general
According to source code, add something like:
Every 60 seconds the watchdog tries to establish a new connection to the database.
If the database is still down - the watchdog repeats alerts sending, but not often than every 15 minutes.

natalja.cernohajeva: corresponding page has been updated with the required info for all supported versions:
2.2;
3.0;
3.4;
4.0.
RESOLVED

<viktors.tjarve> CLOSED

Another use case is a DNS name for DBHost server config parameter and temporary not available DNS server.
Of course it's related to ZBXNEXT-1002

Would be nice for such cases if extended "database is down" message would include a hint that problem is in hostname resolution.

Although, in such case zabbix server continue to be working with database, but in the same time it sends alerts that "db is down" - so it may mislead.
Not sure how it could be resolved technically.

Hi
I've made a simple code for 3.2 to specify an accurate subject and message. I've tried to specify what was written in the specification, but it's difficult to know exactly what is the error message and the database type.

Is it really secure to show such information?

vjaceslavs If we call adding log entry "showing", then yes, no problem with that.

curious, what is the added "Z4" in the summary ?
palivoda dont worry. just a marker for manager.

palivoda, to clarify, this is about the email that is sent out[1], not about any messages in the frontend. the message is sent only to a predefined list of users, "zabbix administrators" by default.

[1] http://www.zabbix.org/wiki/Docs/specs/ZBXNEXT-970

palivoda Yes, check ZBXNEXT-970 Provide more details in DB down message.pdf

Thank you for publishing the specification!

I can imagine a situation where it is not obvious which instance of Zabbix server a database belongs to. Some kind of identifier (which does not exist yet) could be useful. Or you could argue people should name their databases accordingly.

viktors.tjarve We had a discussion about such identifier for Zabbix server. Unfortunately it was decided that for this development it is out of scope.

why not include server hostname ? that should be good for most of the users without hardcoding it in the "from" address or somewhere else

What if there is no hostname, the host name is not speaking or multiple servers are running on the same host? I think I would rather have something I can specify myself.

oh, absolutely a server id/token would be better, but that's out of scope, as mentioned by Viktors. hostname would be a simpler addition that would cover some 90% of the users

There can be all kinds of complicated infrastructure configurations. The scope of this ZBXNEXT is to cover only the case when it is possible to identify both Zabbix DB and Zabbix server using this DB just from DB parameters.
It is decided that other scenarios can be investigated and solved as a different ZBXNEXT.

Released in:

• 4.0.0alpha1 r75597

Released in:

• 4.0.0alpha1 r75965