The SNMP Traps tab provides a self-service interface to configure how incoming SNMP traps are interpreted and converted into alerts as part of monitoring. You can upload MIB files, manage trap definitions, and customize alert behavior across different scopes without impacting other environments.

This feature enables faster onboarding of SNMP traps, greater flexibility in configuration, and improved control over alert generation.

Key capabilities

SNMP traps feature provides the following benefits:

  • Faster onboarding of SNMP traps without backend dependency
  • Greater control over how traps are converted into alerts
  • Flexibility to customize configurations for different environments
  • Improved alert quality by reducing noise and irrelevant events
  • Ability to tailor monitoring behavior at different scopes

Use cases

Use the SNMP Traps feature when you want to:

  • Onboard SNMP traps for a new vendor device using its MIB files
  • Customize severity or alert content for specific traps
  • Apply different alert behavior for different clients or environments
  • Exclude traps that generate excessive or unnecessary alerts
  • Map recovery traps to automatically clear alerts (for example, Critical to OK transitions)
  • Generate separate alerts based on alert component for the same trap OID
  • Map alerts to the actual source device using sender VarOID instead of the trap forwarder

Workflow

The workflow describes how SNMP traps are onboarded, configured, and processed into alerts:

  1. Upload MIB files or use existing trap definitions
  2. The system parses the MIB files and lists available traps
  3. Review and optionally edit trap definitions
  4. Configure processing behavior such as severity and alert content
  5. Save the configuration to the current scope (based on navigation context)
  6. Changes are synchronized through a backend process and may take up to 8 hours to reflect on all gateways
  7. Incoming SNMP traps are processed and converted into alerts