Ad Widget

Collapse

Clone Trigger Using API?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • glenzer2020
    Junior Member
    • Sep 2020
    • 1

    #1

    Clone Trigger Using API?

    Hello. I'm relatively new to Zabbix and have a condition I need to migrate from another monitoring system to Zabbix. With our current monitoring, we have policies deployed to our Linux and Unix hosts for monitoring the file system utilization of various file systems. The current policy in the legacy monitor allows for sending alerts for some specified file systems to our Unix admins, and for other DB file systems to the DBAs. We want to replicate this behavior in Zabbix since DBAs shouldn't get alerts for non-DB file systems, and vice-versa for the Unix admins. The potential solution one of our Zabbix admins came up with is to clone the Mounted Filesystem Discovery trigger after low level discovery, set a tag on the cloned trigger "-tagged" and then use that tag in the alerting action to send to the right group. The original trigger created in low level discovery would then be disabled so that the new cloned trigger would be the only one to take effect.

    Doing this will require a lot of one-time manual steps, so I was looking through the API to see if there is a way to do the cloning of the trigger via API which we might be able to execute with Ansible. I did not find anything about cloning the triggers in the API guide for 4.0.x. But being somewhat of a newb, it's possible I'm missing something about cloning items via the API.

    Any recommendations for either doing the clone of the trigger, or better ways of addressing our need to have different file systems alert different groups?
Working...