Skip to content
TheChatArchiveThe Chat Archive
Perplexitysonar-reasoning· PerplexityHugging Face LMArena Search Arena 24K

How can I change it so that zabbix only notifies me about problems with CRITICAL…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Perplexitysonar-reasoning-pro-high’s answer.
  1. 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?

  2. Perplexity Assistant

    To configure Zabbix to notify only for CRITICAL severity problems and handle other severities differently, follow these steps:


    1. Modify Trigger Action Conditions

    1. Navigate to Trigger Actions:
      Go to Alerts > Actions > Trigger actions and select the existing action (or create a new one)[1][4].
    2. 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.

    2. Adjust Notification Operations

    1. 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].
    2. Optional Escalations:
      For non-CRITICAL issues, create separate actions with different severity conditions (e.g., Average or Warning) 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

    ComponentSettingPurpose
    Trigger ActionCondition: Trigger severity = HighFilters notifications to CRITICAL
    Message TemplateCustomized for CRITICAL alertsProvides detailed context for issues
    Escalation RulesSeparate actions for lower severitiesRoutes 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].

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.