Plugin: go.d.plugin Module: snmp_traps
Attribute each trap to the right Netdata node. When enrichment resolves the trap source to an unambiguous vnode, the trap and any profile metrics attach to that node; otherwise a bounded source label is used.
Netdata matches the trap source identity against known vnodes and host scopes, falling back to a bounded source label when attribution is ambiguous.
This integration is supported on all platforms.
This integration supports multiple instances configured side-by-side.
Always on; attribution uses the configured vnodes and host scopes.
The default configuration for this integration does not impose any limits.
The default configuration for this integration is not expected to impose a significant performance impact on the system.
You can configure the snmp_traps collector in two ways:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for snmp_traps, then click + to add a job. |
| File | If 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.
SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site’s SNMP hub.
Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.
Configure the snmp_traps collector from the Netdata web interface:
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
There are no configuration examples.
There are no alerts configured by default for this integration.
Want a personalised demo of Netdata for your use case?