Reference

Components

prometheus

prometheus.exporter.snmp

General availability (GA) Open source

`prometheus.exporter.snmp`

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

Note
prometheus.exporter.snmp uses the latest configuration introduced in version v0.29.0 of the Prometheus snmp_exporter.

Usage

prometheus.exporter.snmp "<LABEL>" {
  config_file = "<SNMP_CONFIG_FILE_PATH>"

  target "<TARGET_NAME>" {
    address = "<TARGET_ADDRESS>"
  }
}

prometheus.exporter.snmp "<LABEL>" {
  config_file = "<SNMP_CONFIG_FILE_PATH>"
  targets     = <TARGET_LIST>
}

Arguments

You can use the following arguments with prometheus.exporter.snmp:

Name	Type	Description	Default	Required
`concurrency`	`int`	SNMP exporter concurrency.	`1`	no
`config_file`	`string`	SNMP configuration file defining custom modules.		no
`config_merge_strategy`	`string`	A strategy defining how `config` or `config_file` contents merge with the embedded SNMP config. Can be `replace` or `merge`.	`"replace"`	no
`config`	`string` or `secret`	SNMP configuration as inline string.		no
`targets`	`list(map(string))`	SNMP targets.		no

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

The config argument must be a YAML document as string defining which SNMP modules and authorizations to use. config is typically loaded by using the exports of another component. For example,

local.file.LABEL.content
remote.http.LABEL.content
remote.s3.LABEL.content

Set config_merge_strategy to merge to add additional configuration to the embedded SNMP configuration. For example, if you need to add a few custom auth settings without regenerating the whole configuration.

The targets argument is an alternative to the target block. This is useful when SNMP targets are supplied by another component. The following labels can be set to a target:

name: The name of the target (required).
address or __address__: The address of SNMP device (required).
module: SNMP modules to use for polling, separated by comma.
auth: The SNMP authentication profile to use.
walk_params: The configuration to use for this target.

Any other labels defined are added to the scraped metrics.

Blocks

You can use the following blocks with prometheus.exporter.snmp:

Name	Description	Required
`target`	Configures an SNMP target.	no
`walk_param`	SNMP connection profiles to override default SNMP settings.	no

`target`

The target block defines an individual SNMP target. The target block may be specified multiple times to define multiple targets. The label of the block is required and is used in the target’s job label.

Name	Type	Description	Default	Required
`address`	`string`	The address of SNMP device.		yes
`auth`	`string`	SNMP authentication profile to use.	`""`	no
`labels`	`map(string)`	Map of labels to apply to all metrics captured from the target.	`""`	no
`module`	`string`	SNMP modules to use for polling, separated by comma.	`""`	no
`snmp_context`	`string`	Override the `context_name` parameter in the SNMP configuration file.	`""`	no
`walk_params`	`string`	Config to use for this target.	`""`	no

`walk_param`

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.

Name	Type	Description	Default	Required
`max_repetitions`	`int`	How many objects to request with GET/GETBULK.	`25`	no
`name`	`string`	Name of the module to override.		no
`retries`	`int`	How many times to retry a failed request.	`3`	no
`timeout`	`duration`	Timeout for each individual SNMP request.		no

Exported fields

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

Name	Type	Description
`targets`	`list(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 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 doesn’t expose any component-specific debug information.

Debug metrics

prometheus.exporter.snmp doesn’t expose any component-specific debug metrics.

Example

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

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

    target "network_switch_1" {
        address     = "192.168.1.2"
        module      = "system,if_mib"
        walk_params = "public"
        labels = {
            "env" = "dev",
        }
    }

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

    walk_param "private" {
        retries = "2"
    }

    walk_param "public" {
        retries = "2"
    }
}

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

The following example uses an embedded configuration with secrets:

local.file "snmp_config" {
    filename  = "snmp_modules.yml"
    is_secret = true
}

prometheus.exporter.snmp "example" {
    config = local.file.snmp_config.content

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

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

    walk_param "private" {
        retries = "2"
    }

    walk_param "public" {
        retries = "2"
    }
}

// Configure a prometheus.scrape component to collect SNMP metrics.
prometheus.scrape "demo" {
    targets    = prometheus.exporter.snmp.example.targets
    forward_to = [prometheus.remote_write.demo.receiver]
}

prometheus.remote_write "demo" {
    endpoint {
        url = "<PROMETHEUS_REMOTE_WRITE_URL>"

        basic_auth {
            username = "<USERNAME>"
            password = "<PASSWORD>"
        }
    }
}

Replace the following:

<PROMETHEUS_REMOTE_WRITE_URL>: The URL of the Prometheus remote_write compatible server to send metrics to.
<USERNAME>: The username to use for authentication to the remote_write API.
<PASSWORD>: The password to use for authentication to the remote_write API.

The following example uses the alternative way to pass targets:

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

    targets = [
        {
            "name"        = "network_switch_1",
            "address"     = "192.168.1.2",
            "module"      = "system,if_mib",
            "walk_params" = "public",
            "env"         = "dev",
        },
        {
            "name"        = "network_router_2",
            "address"     = "192.168.1.3",
            "module"      = "system,if_mib,mikrotik",
            "walk_params" = "private",
        },
    ]

    walk_param "private" {
        retries = "2"
    }

    walk_param "public" {
        retries = "2"
    }
}

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

The following example uses the local.file component to read targets from a YAML file and send them to the prometheus.exporter.snmp component:

local.file "targets" {
  filename = "targets.yml"
}

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

    targets = encoding.from_yaml(local.file.targets.content)

    walk_param "private" {
        retries = "2"
    }

    walk_param "public" {
        retries = "2"
    }
}

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

The YAML file in this example looks like this:

- name: t1
  address: localhost:161
  module: default
  auth: public_v2
- name: t2
  address: localhost:161
  module: default
  auth: public_v2

The following example uses the discovery.file component to send targets to the prometheus.exporter.snmp component:

discovery.file "example" {
  files = ["targets.yml"]
}

prometheus.exporter.snmp "example" {
  config_file = "snmp_modules.yml"
  targets = discovery.file.example.targets
}

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

The YAML file in this example looks like this:

- targets:
  - localhost:161
  labels:
    name: t1
    module: default
    auth: public_v2
- targets:
  - localhost:161
  labels:
    name: t2
    module: default
    auth: public_v2

Compatible components

prometheus.exporter.snmp has exports that can be consumed by the following components:

Components that consume Targets

Note
Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.

Was this page helpful?

Suggest an edit in GitHub

Create a GitHub issue

Email docs@grafana.com

Help and support

Community

prometheus.exporter.snmp

Usage

Arguments

Blocks

target

walk_param

Exported fields

Component health

Debug information

Debug metrics

Example

Compatible components

Was this page helpful?

Related resources from Grafana Labs

`prometheus.exporter.snmp`

`target`

`walk_param`