Hey all,
Ran into a problem with my zabbix install (about 150 hosts, 11300 triggers, postgresql with timescaledb), in which I would delete hosts, and the next discovery cycle the host comes back, either with it's hostname, or as a ghost IP address.
I found a workaround for that seems to work, and that is to go in to the database and
and then delete it from the zabbix web UI.
I mean, I can do this, but it just seems a bit low-level for an enterprise-grade monitoring system to have to go into the database and delete a line from a table in order to delete a host. It is kind of like having to have the flight crew of your brand new shiny Airbus A380 having to hand crank the landing gear down before landing.
Is there a way to do this from the UI or a setting that can be tweaked, or is this something that I should file a bug on?
Thanks,
--vr
Ran into a problem with my zabbix install (about 150 hosts, 11300 triggers, postgresql with timescaledb), in which I would delete hosts, and the next discovery cycle the host comes back, either with it's hostname, or as a ghost IP address.
I found a workaround for that seems to work, and that is to go in to the database and
Code:
delete from dservices where ip like '192.168.108.13';
I mean, I can do this, but it just seems a bit low-level for an enterprise-grade monitoring system to have to go into the database and delete a line from a table in order to delete a host. It is kind of like having to have the flight crew of your brand new shiny Airbus A380 having to hand crank the landing gear down before landing.
Is there a way to do this from the UI or a setting that can be tweaked, or is this something that I should file a bug on?
Thanks,
--vr