Skip to content

redis_exporter job from prometheus/30.3.0

Github source: d0e6d65 or master branch

Properties

redis_exporter

debug

Output verbose debug information

Default
false

export_client_list

Whether to scrape Client List specific metrics

Default
false

include_system_metrics

Whether to include system metrics like e.g. redis_total_system_memory_bytes

Default
false

is_tile38

Whether to scrape Tile38 specific metrics

Default
false

log_format

Log format, valid options are txt and json

namespace

Namespace for metrics

redis

address

Address of one or more redis nodes, separated by separator

check_keys

Comma separated list of key-patterns to export value and length/size, searched for with SCAN

check_single_keys

Comma separated list of single keys to export value and length/size

check_single_streams

Comma separated list of single streams to export info about streams, groups and consumers

check_streams

Comma separated list of stream-patterns to export info about streams, groups and consumers, searched for with SCAN

config_command

What to use for the CONFIG command

connection_timeout

Timeout for connection to Redis instance

count_keys

Comma separated list of patterns to count

password

Password for one or more redis nodes, separated by separator

script

Lua Redis script for collecting extra metrics

skip_tls_verification

Whether to to skip TLS verification

Default
false
user

User name to use for authentication (Redis ACL for Redis 6.0 and newer)

redis_only_metrics

Whether to export go runtime metrics also

Default
false

web

port

Port on which to expose web interface and telemetry

Default
"9121"
telemetry_path

Path under which to expose metrics

Templates

Templates are rendered and placed onto corresponding instances during the deployment process. This job's templates will be placed into /var/vcap/jobs/redis_exporter/ directory (learn more).

  • bin/redis_exporter_ctl (from bin/redis_exporter_ctl)
  • config/script (from config/script)

Packages

Packages are compiled and placed onto corresponding instances during the deployment process. Packages will be placed into /var/vcap/packages/ directory.