Prometheus SNMP exporter

Switches, routers and other infrastructure often expose their counters through SNMP rather than a Prometheus endpoint. SNMP Exporter queries those devices and translates selected observations into Prometheus metrics, letting teams monitor network equipment alongside applications and hosts. A separate generator helps build the device-specific collection configuration. Choose the counters and authentication profile deliberately: broad collection can burden a device, and older SNMP community-string authentication does not encrypt the credentials traveling across the network.

Current guidance

The recovered entry describes Prometheus snmp_exporter and its separate configuration generator. Current upstream maps device MIB/OID data into labeled metrics and separates the selected module from the authentication profile used for a request. The archived chart’s bundled snmp.yml should not be assumed compatible with every newer exporter or device firmware.

Choose device-specific modules rather than walking every available OID by default. Broad walks increase device load and series volume, while interface labels may change after replacement or reboot. Upstream notes that SNMP v1/v2c community strings travel unencrypted; use an appropriate SNMPv3 configuration where authenticated and private transport is required.

Preserve generator inputs, vendor MIBs, auth profiles and relabeling rules as reviewed configuration. Regenerate with a matching tool version, then compare interface counters and labels against one representative device before expanding the target set. Restrict access to the exporter’s target-selecting endpoint and verify timeouts for unreachable devices. Moving a ConfigMap into a new chart is not evidence that rate calculations or network-device access remain correct.