Zabbix 5.0.3 showing different severity for trigger than the configured one.

[[email protected]]

Hi,

We have Zabbix 5.0.3. For some of the custom checks for servers for certificate expiry severity is showing as Not classified, actually for that trigger severity is set as High.

Could you please help us figure out what might be causing this issue with severity?

[Markku]

Did you change the severity of the trigger configuration after the problem had been raised? Any changes in trigger won't be updated in existing problems, and your problem seems to be over three months old.

Markku

[[email protected]]

The trigger was in High severity from beginning, for other servers it is working fine only for few servers showing the trigger as Not classified.

[Markku]

In that case, did you actually check that the problems have been created by that particular trigger, and not for example a trigger defined in another template?

Classic example: the template you showed is "Template OS Linux - Active Checks", and someone has used template "Template OS Linux - Passive Checks" (etc) for those few servers, and that template has different trigger configuration.

Markku

[[email protected]]

You are right the perfectly working servers are using a different template. How could we correct this for the wrongly reporting template, trigger is configured as High only but showing Not classified? Any idea?

[Markku]

In the Problems page select the problems and click Mass update, then change the severity to your liking.

Markku

[[email protected]]

It asked for a message to update, and in dashboard now that message is showing under Actions. Still the severity is Not classified.

[[email protected]]

Oh it worked, we have to update the severity in the update window and update. Thanks Markku