Menu

Caution

Grafana Alloy is the new name for our distribution of the OTel collector. Grafana Agent has been deprecated and is in Long-Term Support (LTS) through October 31, 2025. Grafana Agent will reach an End-of-Life (EOL) on November 1, 2025. Read more about why we recommend migrating to Grafana Alloy.

Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.

Open source

prometheus.exporter.snmp

The prometheus.exporter.snmp component embeds snmp_exporter. snmp_exporter lets you collect SNMP data and expose them as Prometheus metrics.

Usage

river
prometheus.exporter.snmp "LABEL" {
  config_file = "PATH_SNMP_CONFIG_FILE"
  
  target "TARGET_NAME" {
    address = "TARGET_ADDRESS" 
  }

  walk_param "PARAM_NAME" {
  }
  
  ...
}

Arguments

The following arguments can be used to configure the exporter’s behavior. Omitted fields take their default values.

NameTypeDescriptionDefaultRequired
config_filestringSNMP configuration file defining custom modules.yes

The config_file argument points to a YAML file defining which snmp_exporter modules to use. See snmp_exporter for details on how to generate a config file.

Blocks

The following blocks are supported inside the definition of prometheus.exporter.snmp to configure collector-specific options:

HierarchyNameDescriptionRequired
targettargetConfigures an SNMP target.yes
walk_paramwalk_paramSNMP connection profiles to override default SNMP settings.no
walk_param > authauthConfigure auth for authenticating to the endpoint.no

target block

The target block defines an individual SNMP target. The target block may be specified multiple times to define multiple targets.

NameTypeDescriptionDefaultRequired
namestringName of a snmp_target.yes
addressstringThe address of SNMP device.yes
modulestringSNMP module to use for polling.""no
walk_paramsstringConfig to use for this target.""no

walk_param block

The walk_param block defines an individual SNMP connection profile that can be used to override default SNMP settings. The walk_param block may be specified multiple times to define multiple SNMP connection profiles.

NameTypeDescriptionDefaultRequired
namestringName of the module to override.no
versionintSNMP version to use2no
max_repetitionsintHow many objects to request with GET/GETBULK.25no
retriesintHow many times to retry a failed request.3no
timeoutdurationTimeout for each individual SNMP request.no
authauthConfigure auth for walk param.no

version 1 will use GETNEXT, 2 and 3 use GETBULK.

auth block

The auth block defines an individual SNMP authentication profile that can be used to override default SNMP auth settings.

NameTypeDescriptionDefaultRequired
communitysecretCommunity string is used with SNMP v1 and v2."public"no
usernamestringNetSNMP username."user"no
security_levelstringNetSNMP security_level.noAuthNoPrivno
passwordsecretNetSNMP password.""no
auth_protocolstringNetSNMP auth protocol."MD5"no
priv_protocolstringNetSNMP privacy protocol."DES"no
priv_passwordsecretNetSNMP privacy password.""no
context_namestringNetSNMP context name.""no

username is required if v3 is used. -u option to NetSNMP. security_level can be noAuthNoPriv, authNoPriv or authPriv. -l option to NetSNMP. password is also known as authKey. Is required if security_level is authNoPriv or authPriv. -a option to NetSNMP. auth_protocol is used if security_level is authNoPriv or authPriv. Possible values are MD5, SHA, SHA224, SHA256, SHA384, or SHA512. -a option to NetSNMP. priv_protocol is used if security_level is authPriv. Possible values are DES, AES, AES192, or AES256. -x option to NetSNMP. priv_password is also known as privKey. Is required if security_level is authPriv. -x option to NetSNMP. context_name is required if context is configured on the device. -n option to NetSNMP.

Exported fields

The following fields are exported and can be referenced by other components.

NameTypeDescription
targetslist(map(string))The targets that can be used to collect exporter metrics.

For example, the targets can either be passed to a discovery.relabel component to rewrite the targets’ label sets, or to a prometheus.scrape component that collects the exposed metrics.

The exported targets will use the configured in-memory traffic address specified by the run command.

Component health

prometheus.exporter.snmp is only reported as unhealthy if given an invalid configuration. In those cases, exported fields retain their last healthy values.

Debug information

prometheus.exporter.snmp does not expose any component-specific debug information.

Debug metrics

prometheus.exporter.snmp does not expose any component-specific debug metrics.

Example

This example uses a prometheus.scrape component to collect metrics from prometheus.exporter.snmp:

river
prometheus.exporter.snmp "example" {
	config_file = "snmp_modules.yml"

	target "network_switch_1" {
		address     = "192.168.1.2"
		module      = "if_mib"
		walk_params = "public"
	}

	target "network_router_2" {
		address     = "192.168.1.3"
		module      = "mikrotik"
		walk_params = "private"
	}

	walk_param "private" {
		version = "2"

		auth {
			community = "secret"
		}
	}

	walk_param "public" {
		version = "2"

		auth {
			community = "public"
		}
	}
}
// Configure a prometheus.scrape component to collect SNMP metrics.
prometheus.scrape "demo" {
	targets    = prometheus.exporter.snmp.example.targets
	forward_to = [ /* ... */ ]
}