Hello all,
We are using Zabbix 7.0 LTS (current version of server is 7.0.8). I'm trying to focus alerting on services instead of triggers. It works well after a good tagging of everything BUT I'm facing an issue with some ghost events.
Some service raises a status related to an event I could not browse anymore. A simple way to reproduce is to have a trigger that match on a host and disable this host before it has been resolved.
In problem view everything has disappeared. But in service view my status stays unchanged. The event / trigger is still referenced but when I click on it it displays nothing.

I found a workaround that is not working anymore. I took the trigger_id in the url and close all events associated through API. But it doesn't work anymore or in the current trigger I'm currently having.
Disabled host is not the only reason of having ghost event like that but I've not identified it clearly.
Is there any reason of this behavior ?
Thank you.
We are using Zabbix 7.0 LTS (current version of server is 7.0.8). I'm trying to focus alerting on services instead of triggers. It works well after a good tagging of everything BUT I'm facing an issue with some ghost events.
Some service raises a status related to an event I could not browse anymore. A simple way to reproduce is to have a trigger that match on a host and disable this host before it has been resolved.
In problem view everything has disappeared. But in service view my status stays unchanged. The event / trigger is still referenced but when I click on it it displays nothing.
I found a workaround that is not working anymore. I took the trigger_id in the url and close all events associated through API. But it doesn't work anymore or in the current trigger I'm currently having.
Disabled host is not the only reason of having ghost event like that but I've not identified it clearly.
Is there any reason of this behavior ?
Thank you.
Comment