Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-10227

Close problems and send notifications before host is completely deleted

XMLWordPrintable

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 7.0.18
    • Server (S)
    • None

      Currently, when host is deleted all related entities are gone. It would be nice to have an option to choose if removing hosts from zabbix should resolve all ongoing issues first.

      Such scenario could be useful if problems are tightened to ticketing systems. It would allow to close problems on the other side via webhooks.

      API workarounds using event.acknowledge followed by host.delete are not feasible because that means we would need to wait a moment for trigger action to complete before deleting host but in the mean time, another problem can be raised from the same host. Cancelled escalations don't seem like a solution neither.

      Possibly best to implement this server side, i.e. flag host for deletion, close open problems and send notifications and then finally remove host and problems.

            wiper Andris Zeila
            mkudlacz Michal Kudlacz
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: