Who sets the criticality level of triggers in Zabbix?

Question

linux

Good day, dear All.
And share your experience, who cares - who sets the level of criticality of triggers in Zabbix depending on the host?
Actually, the question is as follows: triggers in Zabbix, as you know, have an event severity level - from Information to Disaster. It is set in the properties of the trigger and usually through templates.
But the nuance is that the same event for different hosts can have a completely different level of criticality. For example, the lack of disk space on one of the secondary development servers is of no interest to anyone except the developers living there and may well carry the level of a light warning: we'll come in the morning, they say, we'll fix it. And the same lack of space on the combat server of the Main Database must have a level not lower than Critical, and when this trigger is triggered at 3 o'clock in the morning, all admins must fly up a meter above the bed.
Although, theoretically, no one prevents these servers from being monitored from one Linux Server template - why not?
Who is solving this problem? Create a template for each group of servers? It gets very oily. Prescribe triggers by hand? Complete nonsense, templates are invented for this.
From the same series - rebooting the server, not responding to pings, changing the status of the interface on the switch, and so on.

Answer 1

Make triggers with expressions that operate not with constants, but with macros - in this case, you can set your trigger threshold for each host, and leave the level the same. All this can be configured even more flexibly by combining it with notification rules, setting different actions and delays before sending for different groups of hosts.

Answer 2

We have zabbix integrated with the incident handling system. In zabbix, various actions are started that check the host group with the problem, and start an incident of the corresponding priority.