Skip to content

SNMP Exporter

Overview

The Prometheus SNMP Exporter polls configured OIDs and exposes them as Prometheus metrics. It is the primary collection method for network and security devices and supplements several UC and infrastructure exporters.

How It Works

  1. Inventory provides the target and standard labels.
  2. A Prometheus scrape job selects the target file and SNMP module.
  3. Prometheus calls the exporter with the target and module.
  4. The exporter polls the device and returns metrics.
  5. Prometheus adds scrape labels and remote-writes the samples to Mimir.

Scrape modules and intervals are device-specific. Check the matching audit YAML and deployed scrape-job configuration rather than assuming one global value.

Supported Devices

The current audit records SNMP collection for CUCM, CUC, IM&P, CER, ASA, ASR, CSR, CUBE, CUSP, FTD/FMC/Firepower, ISE PSN, Linux utilities, MDS, MSW, Nexus leaf/spine, UCS standalone, and UCSM.

Configuration

SNMP modules, credentials, scrape jobs, and target selection are managed through the observability chart/config repositories and generated inventory. Credentials must remain in approved secret storage and must never be added to this repository.

Metrics Format

<metric_name>{device_type="<type>",node_type="<role>",region="<region>",device_name="<name>"} <value>

For failures, check target discovery, network/ACL reachability, SNMP version and credential reference, selected module/OIDs, scrape timeout, and exporter logs.