I'm using Zabbix 4.4
My specific use case is this:
OpenLDAP servers doing replication. One set of two machines for dev work and a set of three for production. The best way we've found to check replication status is to look at the ldap attributed called 'contextCSN'. It's a text string that looks like this:
20200124234257.174629Z#000000#000#000000
I'm collecting that attribute for each of the servers. The challenge is now how to create a trigger from that. Right now I'm playing with a trigger on the zabbix host that tries to compare the value from the two dev servers. If they're not equal, that generates a trigger.
{ldapdev1:ldap.contextcsn.last()}<>{ldapdev2:ldap. contextcsn.last()}
The <> apparently only works on numeric values, so this actually isn't working.
What I'm hoping for:
1. Check the value for all hosts in a hostgroup (can be individual hosts, but not ideal)
2. If they're not all the same (over a five minute period to account for legit sync changes), generate a trigger. Maybe checking over time isn't possible. Might be something that can be handled in the action.
Any insight on how to make this work is appreciated.
- Steve
My specific use case is this:
OpenLDAP servers doing replication. One set of two machines for dev work and a set of three for production. The best way we've found to check replication status is to look at the ldap attributed called 'contextCSN'. It's a text string that looks like this:
20200124234257.174629Z#000000#000#000000
I'm collecting that attribute for each of the servers. The challenge is now how to create a trigger from that. Right now I'm playing with a trigger on the zabbix host that tries to compare the value from the two dev servers. If they're not equal, that generates a trigger.
{ldapdev1:ldap.contextcsn.last()}<>{ldapdev2:ldap. contextcsn.last()}
The <> apparently only works on numeric values, so this actually isn't working.
What I'm hoping for:
1. Check the value for all hosts in a hostgroup (can be individual hosts, but not ideal)
2. If they're not all the same (over a five minute period to account for legit sync changes), generate a trigger. Maybe checking over time isn't possible. Might be something that can be handled in the action.
Any insight on how to make this work is appreciated.
- Steve