In my Zabbix setup, when a port goes down, a trigger is invoked, which executes a trigger action. This action runs a script on the Zabbix server to update the health_status column in my RDS table to "inactive." However, when I try to kill ports on all servers simultaneously using a script, it takes 13 seconds to update all table columns to "inactive." What solution can achieve this update within 2 seconds?
I configured a Zabbix trigger to execute an action that runs a script on the Zabbix server. This script updates the health_status column in my RDS table to "inactive" when a port goes down. I tested this by simulating port failures on multiple servers simultaneously using a script.
When I kill the port on an individual server, the RDS table updates in less than 1.5 seconds. However, when killing ports on all servers simultaneously, it takes around 13 seconds to update all the columns. I expected the updates to occur within 2 seconds for all servers, but the delay is much longer. I’m looking for a solution to optimize the performance for simultaneous updates.
I configured a Zabbix trigger to execute an action that runs a script on the Zabbix server. This script updates the health_status column in my RDS table to "inactive" when a port goes down. I tested this by simulating port failures on multiple servers simultaneously using a script.
When I kill the port on an individual server, the RDS table updates in less than 1.5 seconds. However, when killing ports on all servers simultaneously, it takes around 13 seconds to update all the columns. I expected the updates to occur within 2 seconds for all servers, but the delay is much longer. I’m looking for a solution to optimize the performance for simultaneous updates.