Skip to main content

Fortinet Inc SNMP Traps

Plugin: go.d.plugin Module: snmp_traps

Overview

Receive, decode, and store SNMP traps and INFORMs from Fortinet Inc devices with Netdata. The bundled Fortinet Inc trap profile decodes 338 trap definitions across 18 MIBs into structured journal events with named, typed varbinds — searchable and filterable in the Logs tab.

Netdata's SNMP trap listener receives traps on UDP/162, matches them to the Fortinet Inc enterprise OID space, and decodes the varbinds using the bundled Fortinet Inc trap profile. No per-trap configuration.

This integration is supported on all platforms.

This integration supports multiple instances configured side-by-side.

Default Behavior

Auto-Detection

Traps from Fortinet Inc devices are decoded automatically once the device is pointed at the Agent's trap listener.

Limits

The default configuration for this integration does not impose any limits.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup

You can configure the snmp_traps collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp_traps, then click + to add a job.
FileIf you prefer configuring via file, or need to automate deployments (e.g., with Ansible)Edit go.d/snmp.conf and add a job.
important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

SNMP access

SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site's SNMP hub.

Configuration

Options

Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.

via UI

Configure the snmp_traps collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp_traps data-collection job to run and click the (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type snmp_traps (or scroll the list) to locate the snmp_traps collector.
  5. Click the + next to the snmp_traps collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/snmp.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
Examples

There are no configuration examples.

Alerts

There are no alerts configured by default for this integration.

Metrics

Netdata decodes 338 trap definitions from Fortinet Inc across 18 MIBs into structured journal events. A trap is decoded only if the device actually sends it; inclusion here means the profile can decode it.

By severity: emerg 1 · alert 61 · crit 15 · warning 182 · notice 75 · info 4

By category: state_change 91 · config_change 19 · security 79 · auth 5 · license 6 · mobility 1 · diagnostic 137

Coverage by MIB

MIBTrap definitions
FORTINET-FORTIADC-MIB150
FORTINET-FORTIGATE-MIB30
FORTINET-FORTIWEB-MIB27
FORTIOS-300-MIB18
FORTINET-TRAP-MIB-28016
FORTINET-TRAP-MIB15
FORTINET-FORTIMAIL-MIB13
FORTIMAIL-TRAP-MIB-22012
FORTINET-CORE-MIB10
FORTINET-FORTIMANAGER-FORTIANALYZER-MIB8
FORTINET-FORTIAUTHENTICATOR-MIB7
FORTINET-FORTIEXTENDER-MIB7
FORTINET-FORTISANDBOX-MIB7
FORTINET-FORTIANALYZER-MIB5
FORTINET-FORTIAP-MIB5
FORTINET-FORTISWITCH-MIB4
FORTINET-FORTIVOICE-MIB3
FORTINET-300-MIB1

Sample decoded traps

  • FORTINET-TRAP-MIB::fnTrapColdStart
  • FORTINET-TRAP-MIB::fnTrapSystemDown
  • FORTINET-TRAP-MIB::fnTrapAgentDown
  • FORTINET-TRAP-MIB::fnTrapAgentUp
  • FORTINET-TRAP-MIB::fnTrapInfChg

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.