Aggregate triggers to create only one action

[SpeedyGo]

Hello guys,
Among other things, we monitor SQL Server and use the published SQL Server template.
In general, we have defined that an action is triggered for each trigger with a certain severity.
Now an SQL server has several databases. If the SQL backup does not work, a trigger is triggered for each database and several actions are generated.
Is it possible to construct triggers in such a way that they only fire if another trigger created from the same prototype has not already fired? In this way, only one action would be created for a central problem.

Many thanks for your help!

[SanMonitor]

Hey SpeedyGo,

I think dependencies could help you out here?
Go to the trigger prototypes, and for each trigger go to the dependencies tab and add a dependency on your central problem.
Then if the central problem is active, none of the dependent triggers will fire.

[SanMonitor]

Hey SpeedyGo,

I think dependencies could help you out here?
Go to the trigger prototypes, and for each trigger go to the dependencies tab and add a dependency on your central problem.
Then if the central problem is active, none of the dependent triggers will fire.

[SpeedyGo]

Hello SanMonitor,
Thank you for this idea. I will check whether I can create a trigger for this central problem. Then the logic with the dependencies would work.

[SpeedyGo]

Hello SanMonitor,
the problem is more difficult here... In my case I have to monitor an SQL server. On such server I can have multiple instances. That's why I need an LLD to create the triggers via trigger prototypes. To implement your suggestion I have to monitor the SQLServerAgent services. In another LLD will be created items and triggers for SQL jobs. What I would like to achieve is that these job triggers are only fire when the SQLServerAgent service is running. This is the dependency. But Zabbix doesn't allow me to create a dependency to another trigger prototype if this prototype is in another LLD.