Table of Contents
5 Trigger severity
Severity represents the relative importance of a trigger.
Assigning severity is not only useful for visual representation, but also for avoiding notifications on trivial issues.
Trigger severities are used for:
- Visual representation (distinct color per each created problem, based on the original trigger severity)
- Limiting notifications based on severity (see action conditions)
- User media - different media (notification channel) for different severities (for example, SMS for triggers of High and Disaster severity, and Email for triggers of other severities)
- Audio in global alarms - different audio for different severities
The following trigger severities are supported by default:
| Severity | Color | Description |
|---|---|---|
| Not classified | Gray | Can be used where the severity level of an event is unknown, has not been determined, is not part of the regular monitoring scope, etc., for example, during initial configuration, as a placeholder for future assessment, or as part of an integration process. |
| Information | Light blue | Can be used for informational events that do not require immediate attention, but can still provide valuable insights. |
| Warning | Yellow | Can be used to indicate a potential issue that might require investigation or action, but that is not critical. |
| Average | Orange | Can be used to indicate a significant issue that should be addressed relatively soon to prevent further problems. |
| High | Light red | Can be used to indicate critical issues that need immediate attention to avoid significant disruptions. |
| Disaster | Red | Can be used to indicate a severe incident that requires immediate action to prevent, for example, system outages or data loss. |
Trigger severity names and colors can be customized in Administration > General > Trigger displaying options. Colors are shared among all frontend themes.
Translating customized severity names
If Zabbix frontend translations are used, custom severity names will override translated names by default.
Default trigger severity names are available for translation in all locales. If a severity name is changed, a custom name is used in all locales and additional manual translation is needed.
Custom severity name translation procedure:
- set required custom severity name, for example, 'Important'
- edit <frontend_dir>/locale/<required_locale>/LC_MESSAGES/frontend.po
- add 2 lines:
and save file.
- create .mo files as described in <frontend_dir>/locale/README
Here msgid should match the new custom severity name and msgstr should be the translation for it in the specific language.
This procedure should be performed after each severity name change.