Ateme SNMP Traps

Plugin: go.d.plugin Module: snmp_traps

Overview

Receive, decode, and store SNMP traps and INFORMs from Ateme devices with Netdata. The bundled Ateme trap profile decodes 181 trap definitions across 2 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 Ateme enterprise OID space, and decodes the varbinds using the bundled Ateme 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 Ateme 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:

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 :gear: (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.

Metrics

Netdata decodes 181 trap definitions from Ateme across 2 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 6 · crit 4 · err 6 · warning 139 · notice 23 · info 2

By category: state_change 12 · config_change 11 · security 1 · license 11 · diagnostic 146

Coverage by MIB

Sample decoded traps

• TITAN-MIB::alarm
• ATEME-TITAN-EDGE-MIB::titanEdgeApplianceMonitorLogSystemStartedNotification
• ATEME-TITAN-EDGE-MIB::titanEdgeApplianceMonitorLogSystemStoppedNotification
• ATEME-TITAN-EDGE-MIB::titanEdgeApplianceMonitorLogSystemEthernetIgmpVersionChangedNotification
• ATEME-TITAN-EDGE-MIB::titanEdgeApplianceMonitorLogDvbSsuChannelUpdateNotification

Alerts

There are no alerts configured by default for this integration.