Ad Widget

Collapse

Do not get {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} in emails

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • NormanW
    Junior Member
    • Feb 2024
    • 6

    #1

    Do not get {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} in emails

    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.
    Last edited by NormanW; 28-02-2024, 15:23.
  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4806

    #2
    Problem has been resolved at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE} <= no information displayed
    This event has not been recovered yet, so no data is available for that...

    Comment

    • NormanW
      Junior Member
      • Feb 2024
      • 6

      #3
      Ok, thanks. Hm, is there no "LAST.RECOVERY.TIME" or similar?

      Comment

      • cyber
        Senior Member
        Zabbix Certified SpecialistZabbix Certified Professional
        • Dec 2006
        • 4806

        #4
        No... notification is about one particular event, that was just generated... It has no knowledge, if there was previous similar event or not...
        Its the same as if you have broken pipes at home.. You do not know when plumber will arrive and there is absolutely no benefit of knowing, that there was a leak month ago..

        Comment

        • NormanW
          Junior Member
          • Feb 2024
          • 6

          #5
          OK, thanks for the plumber example :-) The plumber may not interest, but we would like to see, in one mail notification, when was the last working status, when the device went offline. This was great to get this information in PRTG Monitoring. Maybe a new feature in the new Zabbix version?
          Meanwhile we will delete this line: <b>Problem has been resolved</b> at {EVENT.RECOVERY.TIME} on {EVENT.RECOVERY.DATE}<br> from our template.

          Thanks for your feedback.

          Comment

          Working...