Hi Zabbix Teams,
we went from PRTG Paessler Monitoring to Zabbix because of our pure Linux Infrastructure now (in the past we used Windows Server as well).
When we got PRTG eMail notifications, we could see when a problem started and when it was resolved, and vice versa. In Zabbix, when we get an email notification when a problem resolved, we can see when the problem started. But not vice versa, means when the problem started, we cannot see when was the last resolve. Here is an example:
This works fine:
Problem has been resolved at 12:01:38 on 2024.02.28
Problem name: Unavailable by ICMP ping
Problem duration: 5h 39m 30s
Host: Server1, 192.168.001.83
Severity: High
Original problem ID: 5467999
Problem started at 06:22:08 on 2024.02.28
And this not:
Problem started at 12:21:38 on 2024.02.28
Problem name: Unavailable by ICMP ping
Host: Server1, 192.168.001.83
Severity: High
Operational data: Down (0)
Original problem ID: 5468374
Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} <= no information displayed
What do we set wrong? Maybe there is an EVENT-LAST-Recovery or so?
This is our problem resolve template:
<b>Problem has been resolved</b> at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}<br>
<b>Problem name:</b> {EVENT.RECOVERY.NAME}<br>
<b>Problem duration:</b> {EVENT.DURATION}<br>
<b>Host:</b> {HOST.NAME}, {HOST.IP}<br><b>Severity:</b> {EVENT.SEVERITY}<br>
<b>Original problem ID:</b> {EVENT.ID}<br>{TRIGGER.URL}
<b>Problem started</b> at {EVENT.TIME} on {EVENT.DATE}<br>
This is our problem started template:
<b>Problem started</b> at {EVENT.TIME} on {EVENT.DATE}<br>
<b>Problem name:</b> {EVENT.NAME}<br>
<b>Host:</b> {HOST.NAME}, {HOST.IP}<br>
<b>Severity:</b> {EVENT.SEVERITY}<br>
<b>Operational data:</b> {EVENT.OPDATA}<br>
<b>Original problem ID:</b> {EVENT.ID}<br>{TRIGGER.URL}
<b>Problem has been resolved</b> at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}<br>
We use Zabbix 6.4.12 on Debian 12 and NGINX PHP 8.3.3.
we went from PRTG Paessler Monitoring to Zabbix because of our pure Linux Infrastructure now (in the past we used Windows Server as well).
When we got PRTG eMail notifications, we could see when a problem started and when it was resolved, and vice versa. In Zabbix, when we get an email notification when a problem resolved, we can see when the problem started. But not vice versa, means when the problem started, we cannot see when was the last resolve. Here is an example:
This works fine:
Problem has been resolved at 12:01:38 on 2024.02.28
Problem name: Unavailable by ICMP ping
Problem duration: 5h 39m 30s
Host: Server1, 192.168.001.83
Severity: High
Original problem ID: 5467999
Problem started at 06:22:08 on 2024.02.28
And this not:
Problem started at 12:21:38 on 2024.02.28
Problem name: Unavailable by ICMP ping
Host: Server1, 192.168.001.83
Severity: High
Operational data: Down (0)
Original problem ID: 5468374
Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} <= no information displayed
What do we set wrong? Maybe there is an EVENT-LAST-Recovery or so?
This is our problem resolve template:
<b>Problem has been resolved</b> at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}<br>
<b>Problem name:</b> {EVENT.RECOVERY.NAME}<br>
<b>Problem duration:</b> {EVENT.DURATION}<br>
<b>Host:</b> {HOST.NAME}, {HOST.IP}<br><b>Severity:</b> {EVENT.SEVERITY}<br>
<b>Original problem ID:</b> {EVENT.ID}<br>{TRIGGER.URL}
<b>Problem started</b> at {EVENT.TIME} on {EVENT.DATE}<br>
This is our problem started template:
<b>Problem started</b> at {EVENT.TIME} on {EVENT.DATE}<br>
<b>Problem name:</b> {EVENT.NAME}<br>
<b>Host:</b> {HOST.NAME}, {HOST.IP}<br>
<b>Severity:</b> {EVENT.SEVERITY}<br>
<b>Operational data:</b> {EVENT.OPDATA}<br>
<b>Original problem ID:</b> {EVENT.ID}<br>{TRIGGER.URL}
<b>Problem has been resolved</b> at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}<br>
We use Zabbix 6.4.12 on Debian 12 and NGINX PHP 8.3.3.
You do not know when plumber will arrive and there is absolutely no benefit of knowing, that there was a leak month ago..
Comment