Recovery time "Never"

XMLWordPrintable

    • Type: Problem report
    • Resolution: Commercial support required
    • Priority: Trivial
    • None
    • Affects Version/s: None
    • Component/s: None
    • None

      Salve, da alcuni giorni sto riscontrando un anomalia sul recovery time di alcuni allarmi, ma non su tutti.
      Se vado a vedere il problem mi risulta ancora in corso ma se apro l'history vedo che รจ in stato resolved con recovery time "never" invece che con un orario specifico.
      Potreste indicarmi il motivo di tale problema ed una eventuale risoluzione?

      La versione di Zabbix 6.0.22., inoltre allego immagine della problematica e di un trigger.

      Saluti e grazie

      ---------
      Google translate:

      Hello, for a few days I have been experiencing an anomaly on the recovery time of some alarms, but not on all of them. If I go to see the problem it appears to be still ongoing but if I open the history I see that it is in resolved status with recovery time "never" instead of a specific time. Could you tell me the reason for this problem and a possible resolution?

      The version of Zabbix 6.0.22., I also attach an image of the problem and a trigger.

      Greetings and thanks

        1. Zabbix data.png
          84 kB
          Leonardo Martelli
        2. Zabbix problem history.png
          13 kB
          Leonardo Martelli
        3. Zabbix problem.png
          13 kB
          Leonardo Martelli
        4. Zabbix trigger.png
          46 kB
          Leonardo Martelli
        5. Zabbix data 17-02.png
          328 kB
          Leonardo Martelli
        6. Zabbix event detail.png
          132 kB
          Leonardo Martelli
        7. Zabbix query sql.png
          299 kB
          Leonardo Martelli
        8. zabbix dettaglio .png
          1.88 MB
          Leonardo Martelli

            Assignee:
            Zabbix Support Team
            Reporter:
            Leonardo Martelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: