How can I change it so that zabbix only notifies me about problems with CRITICAL…
- User
How can I change it so that zabbix only notifies me about problems with CRITICAL sevirity. Or somehow set it up so that these problems are treated differently notifications-wise?
Assistant
To configure Zabbix to notify only for CRITICAL severity problems and handle other severities differently, follow these steps:
1. Modify Trigger Action Conditions
- Navigate to Trigger Actions:
Go toAlerts > Actions > Trigger actionsand select the existing action (or create a new one)[1][4]. - Add Severity Condition:
In the Conditions tab, add a new condition:- Condition Type:
Trigger severity - Condition Value:
High(corresponds to CRITICAL severity)[7].
This ensures the action only triggers for CRITICAL problems.
- Condition Type:
2. Adjust Notification Operations
- Define Operations:
In the Operations tab, specify the notification method (e.g., email, webhook) and message template.- Use message templates to customize alerts for CRITICAL issues[1][2].
- Optional Escalations:
For non-CRITICAL issues, create separate actions with different severity conditions (e.g.,AverageorWarning) and link them to lower-priority notification channels[2][7].
3. Verify Trigger Severity
Ensure triggers are correctly classified as CRITICAL:
- Check Trigger Configuration: Edit the trigger to confirm its severity is set to
High[7]. - Adjust Templates: If triggers inherit severity from templates, modify the template’s trigger severity[3][6].
4. Disable Unwanted Alerts
For persistent non-CRITICAL alerts:
- Disable Triggers: Manually disable triggers for specific hosts or templates[6].
- Modify Discovery Rules: Adjust service/item discovery filters to exclude irrelevant alerts (e.g., exclude "Automatic (Delayed)" services)[6].
Key Configuration Example
Component Setting Purpose Trigger Action Condition: Trigger severity = HighFilters notifications to CRITICAL Message Template Customized for CRITICAL alerts Provides detailed context for issues Escalation Rules Separate actions for lower severities Routes non-CRITICAL alerts to secondary channels
By implementing these steps, Zabbix will prioritize CRITICAL alerts while allowing flexibility for other severities. For persistent false positives, consider refining trigger logic or discovery rules[3][6].
- Navigate to Trigger Actions:
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.