Two Trigger Actions That Do The Same Thing But Only One Works?

[techmattr]

v6.2.2 Ubuntu/Docker

I have two Trigger Actions for reporting HDD space issues. One of them is restricted by Host Group. The SysAdmin - Report HDD Space Problems works but the DBA - Report HDD Space Problems does not. Am I not allowed to have two trigger actions based on the same tags or something? Why would this DBA trigger action not work? There are no failures on the problem that it wasn't able to send or anything. It just shows the successful send from the SysAdmin trigger action.

[Markku]

What are your operations? If you send messages to someone, do they have access to the host groups?

Markku

[techmattr]

What are your operations? If you send messages to someone, do they have access to the host groups?

Markku

So I was going through and collecting screen shots to give you a thorough answer and saw that the Email Media Type I have setup for the DBAs was set to only receive High and Disaster alerts. I'll have to test again but I'm assuming this will start working as long as I select the correct severity.

[techmattr]

I'm still having this issue. I created a new user with Super User role and made sure the media type was set to use all severity levels.
I even created a new media type to make sure there were no overlapping configurations.
At this point it seems Zabbix is just unable to send an alert to multiple trigger actions? Is this correct?

[Markku]

At this point it seems Zabbix is just unable to send an alert to multiple trigger actions? Is this correct?

That's not correct. You have some other problem, you need to check your configurations.

Markku

[techmattr]

I've basically confirmed this is correct. I finally got the secondary trigger action working. I needed to change (Host Group A AND Host Group B) to (Host Group A OR Host Group B). Now that secondary trigger alert gets an email but the first trigger action does not. So only one trigger action can occur per problem. If I disable the second trigger action the first one starts working.

[Markku]

You do understand that your statements do very little for us others when you don't show the actual configurations, right?

Markku

[techmattr]

I have the configs in the first post but I did update them slightly and here are some additional screen shots:

SA Alerts:



DBA alerts:




Essentially these alerts do the exact same thing except one is filtered by two host groups. The SA alerts should be triggering all the same alerts that get triggered by the DBA alerts since the SA alerts trigger encompasses all hosts. However, when I get alerts from the DBA alerts the SA alerts do not send. If I disable the DBA alerts then the SA alerts start working.

I believe this is a bug in how the trigger actions are filtering the host groups as I can produce very strange behavior but playing around with what host groups are or are not filtered.

Additionally I can do something like disabled the DBA alerts, clone the SA alerts and produce duplicate alerts. So the two SA alerts will fire at the same time. But if I add a host group filter to the cloned SA alerts then things start breaking.

Essentially the only way I can consistently get this to work is to make sure there are no overlapping hosts if host group filters are applied. So if I add a host group filter to the DBA alerts then I need to add a host group filter to the SA alerts as well. However, there is a issue with this as well because the Host group does not equal filter seems to do the opposite in the scenario. If I add Host group does not equal Database Prod to the SA alerts then I start getting duplicate alerts. One from DBA and one from SA even though the SA alert says Does NOT equal.

[Markku]

Ok, I don't see the pictures in the post but you should create a minimum reproduceable set of configurations and open an issue at https://support.zabbix.com.

One way to test actions (without using emails or similar) is to create scripts in Zabbix (like "date >> /tmp/action1") and use them in the action instead of "Send message". They are simple to reproduce by the engineers, simple to monitor, and they remove any need for user-specific notification configurations.

Markku

[Markku]

One more thing: if you are still using the 6.2.2 version of Zabbix, the latest is 6.2.6 so it would be best to verify the behaviour with that before opening an issue.

Markku

[techmattr]

Thanks I'll work on those items. I guess I'll need to work on upgrading first.