Documentation

Riak Input Plugin

This plugin gathers metrics from Riak instances.

Introduced in: Telegraf v0.10.4 Tags: server OS support: all

Global configuration options

In addition to the plugin-specific configuration settings, plugins support additional global and plugin configuration settings. These settings are used to modify metrics, tags, and field or create aliases and configure ordering, etc. See the CONFIGURATION.md for more details.

Configuration

# Read metrics one or many Riak servers
[[inputs.riak]]
  # Specify a list of one or more riak http servers
  servers = ["http://localhost:8098"]

Metrics

  • riak:
    • tags:
      • server (host:port of the given server address)
      • nodename (internal node name received)
    • fields
      • cpu_avg1
      • cpu_avg15
      • cpu_avg5
      • memory_code
      • memory_ets
      • memory_processes
      • memory_system
      • memory_total
      • node_get_fsm_objsize_100
      • node_get_fsm_objsize_95
      • node_get_fsm_objsize_99
      • node_get_fsm_objsize_mean
      • node_get_fsm_objsize_median
      • node_get_fsm_siblings_100
      • node_get_fsm_siblings_95
      • node_get_fsm_siblings_99
      • node_get_fsm_siblings_mean
      • node_get_fsm_siblings_median
      • node_get_fsm_time_100
      • node_get_fsm_time_95
      • node_get_fsm_time_99
      • node_get_fsm_time_mean
      • node_get_fsm_time_median
      • node_gets
      • node_gets_total
      • node_put_fsm_time_100
      • node_put_fsm_time_95
      • node_put_fsm_time_99
      • node_put_fsm_time_mean
      • node_put_fsm_time_median
      • node_puts
      • node_puts_total
      • pbc_active
      • pbc_connects
      • pbc_connects_total
      • vnode_gets
      • vnode_gets_total
      • vnode_index_reads
      • vnode_index_reads_total
      • vnode_index_writes
      • vnode_index_writes_total
      • vnode_puts
      • vnode_puts_total
      • read_repairs
      • read_repairs_total

Time fields such as node_get_fsm_time_mean are measured in nanoseconds.

Example Output

riak,nodename=riak@127.0.0.1,server=localhost:8098 cpu_avg1=31i,cpu_avg15=69i,cpu_avg5=51i,memory_code=11563738i,memory_ets=5925872i,memory_processes=30236069i,memory_system=93074971i,memory_total=123311040i,node_get_fsm_objsize_100=0i,node_get_fsm_objsize_95=0i,node_get_fsm_objsize_99=0i,node_get_fsm_objsize_mean=0i,node_get_fsm_objsize_median=0i,node_get_fsm_siblings_100=0i,node_get_fsm_siblings_95=0i,node_get_fsm_siblings_99=0i,node_get_fsm_siblings_mean=0i,node_get_fsm_siblings_median=0i,node_get_fsm_time_100=0i,node_get_fsm_time_95=0i,node_get_fsm_time_99=0i,node_get_fsm_time_mean=0i,node_get_fsm_time_median=0i,node_gets=0i,node_gets_total=19i,node_put_fsm_time_100=0i,node_put_fsm_time_95=0i,node_put_fsm_time_99=0i,node_put_fsm_time_mean=0i,node_put_fsm_time_median=0i,node_puts=0i,node_puts_total=0i,pbc_active=0i,pbc_connects=0i,pbc_connects_total=20i,vnode_gets=0i,vnode_gets_total=57i,vnode_index_reads=0i,vnode_index_reads_total=0i,vnode_index_writes=0i,vnode_index_writes_total=0i,vnode_puts=0i,vnode_puts_total=0i,read_repair=0i,read_repairs_total=0i 1455913392622482332

Was this page helpful?

Thank you for your feedback!


New in InfluxDB 3.5

Key enhancements in InfluxDB 3.5 and the InfluxDB 3 Explorer 1.3.

See the Blog Post

InfluxDB 3.5 is now available for both Core and Enterprise, introducing custom plugin repository support, enhanced operational visibility with queryable CLI parameters and manual node management, stronger security controls, and general performance improvements.

InfluxDB 3 Explorer 1.3 brings powerful new capabilities including Dashboards (beta) for saving and organizing your favorite queries, and cache querying for instant access to Last Value and Distinct Value caches—making Explorer a more comprehensive workspace for time series monitoring and analysis.

For more information, check out:

InfluxDB Docker latest tag changing to InfluxDB 3 Core

On November 3, 2025, the latest tag for InfluxDB Docker images will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments.

If using Docker to install and run InfluxDB, the latest tag will point to InfluxDB 3 Core. To avoid unexpected upgrades, use specific version tags in your Docker deployments. For example, if using Docker to run InfluxDB v2, replace the latest version tag with a specific version tag in your Docker pull command–for example:

docker pull influxdb:2