Hi Forum Team,
I'm hoping someone will be able to help us with the below, as we're not sure we're doing this the best way.
Previously in Zabbix 5, we had Services Setup;I will just use "Active Directory" throughout as an example service - We had this configured with child services which were specific Windows Services running on our domain controllers, when any of these Windows Service stopped running, it flagged as the service down.
We have now moved to Zabbix 6 and understand that this concept has been replaced by Tags, which admittedly we hadn't used prior and are just getting up to speed.
At present what we have done, is on each Domain Controller Zabbix Host we have cloned the trigger of the Windows Service we want to monitor, and then added a tag to that trigger of Service:ActiveDirectory (we did this because as far as we can see we can't add Tags on the Item as its not editable, and we got ValueMap errors when attempting to clone the Item).
This does work in terms of Service Monitoring, but it seems odd as the tag then isn't applied to the problem from what we can see, and also when we go into Services or Monitoring>Latest Data and search for our Service:Application Tag, we can't find them (I'm assuming that's because this searches item tags rather than trigger tags). This has the downside that we can't just search for that tag to see what triggers are part of a certain Service - we have to go into each individual Host and look at the triggers list and the tags column to actually see whats a part of our ActiveDirectory Service tag.
Is there a better way that we should be doing this? I'm sure there likely is but I just can't see it at the moment - any guidance or links would be very much appreciated!
Thanks,
Tim
I'm hoping someone will be able to help us with the below, as we're not sure we're doing this the best way.
Previously in Zabbix 5, we had Services Setup;I will just use "Active Directory" throughout as an example service - We had this configured with child services which were specific Windows Services running on our domain controllers, when any of these Windows Service stopped running, it flagged as the service down.
We have now moved to Zabbix 6 and understand that this concept has been replaced by Tags, which admittedly we hadn't used prior and are just getting up to speed.
At present what we have done, is on each Domain Controller Zabbix Host we have cloned the trigger of the Windows Service we want to monitor, and then added a tag to that trigger of Service:ActiveDirectory (we did this because as far as we can see we can't add Tags on the Item as its not editable, and we got ValueMap errors when attempting to clone the Item).
This does work in terms of Service Monitoring, but it seems odd as the tag then isn't applied to the problem from what we can see, and also when we go into Services or Monitoring>Latest Data and search for our Service:Application Tag, we can't find them (I'm assuming that's because this searches item tags rather than trigger tags). This has the downside that we can't just search for that tag to see what triggers are part of a certain Service - we have to go into each individual Host and look at the triggers list and the tags column to actually see whats a part of our ActiveDirectory Service tag.
Is there a better way that we should be doing this? I'm sure there likely is but I just can't see it at the moment - any guidance or links would be very much appreciated!
Thanks,
Tim
Comment