Hi
Let's say I have a MySQL cluster of around 50 amazon instances that dynamically scale up and down depending on load.
I want to have a trigger in zabbix that checks on a specific return value from a MySQL query on the cluster. Could be getting a
from a table, or checking the status of cluster synchronization (which is done via something like
)
So I add this trigger to my MySQL Cluster Server Zabbix template.
But what I don't want is for all of the 50 servers to generate 50 duplicate pager calls and email alerts whenever this trigger fires – 1 is enough.
What I've done so far is simply creating the trigger directly on a random MySQL node, but then the trigger obviously stops working when auto scaling removes that node/server.
So where do I put my trigger?
Since Zabbix is 100% host-based, I guess I could put it on the Zabbix Server itself, but of course I also autoscale my zabbix environment due to load, and then I have the same problem.
Any pointers on this?
Let's say I have a MySQL cluster of around 50 amazon instances that dynamically scale up and down depending on load.
I want to have a trigger in zabbix that checks on a specific return value from a MySQL query on the cluster. Could be getting a
Code:
COUNT()
Code:
show global status where Variable_name='wsrep_evs_repl_latency'
So I add this trigger to my MySQL Cluster Server Zabbix template.
But what I don't want is for all of the 50 servers to generate 50 duplicate pager calls and email alerts whenever this trigger fires – 1 is enough.
What I've done so far is simply creating the trigger directly on a random MySQL node, but then the trigger obviously stops working when auto scaling removes that node/server.
So where do I put my trigger?
Since Zabbix is 100% host-based, I guess I could put it on the Zabbix Server itself, but of course I also autoscale my zabbix environment due to load, and then I have the same problem.
Any pointers on this?
Comment