Skip to main content
Version: 1.37.x

Pika monitoring with Netdata

Pika is a persistent huge storage service, compatible with the vast majority of redis interfaces (details), including string, hash, list, zset, set and management interfaces.


This module monitors one or more Pika instances, depending on your configuration.

It collects information and statistics about the server executing the following commands:

Metrics

All metrics have "pika." prefix.

MetricScopeDimensionsUnits
connectionsglobalacceptedconnections
clientsglobalconnectedclients
memoryglobalusedbytes
connected_replicasglobalconnectedreplicas
commandsglobalprocessedcommands/s
commands_callsglobala dimension per commandcalls/s
database_strings_keysglobala dimension per databasekeys
database_strings_expires_keysglobala dimension per databasekeys
database_strings_invalid_keysglobala dimension per databasekeys
database_hashes_keysglobala dimension per databasekeys
database_hashes_expires_keysglobala dimension per databasekeys
database_hashes_invalid_keysglobala dimension per databasekeys
database_lists_keysglobala dimension per databasekeys
database_lists_expires_keysglobala dimension per databasekeys
database_lists_invalid_keysglobala dimension per databasekeys
database_zsets_keysglobala dimension per databasekeys
database_zsets_expires_keysglobala dimension per databasekeys
database_zsets_invalid_keysglobala dimension per databasekeys
database_sets_keysglobala dimension per databasekeys
database_sets_expires_keysglobala dimension per databasekeys
database_sets_invalid_keysglobala dimension per databasekeys
uptimeglobaluptimeseconds

Configuration

Edit the go.d/pika.conf configuration file using edit-config from the Netdata config directory, which is typically at /etc/netdata.

cd /etc/netdata # Replace this path with your Netdata config directory
sudo ./edit-config go.d/pika.conf

There are two connection types: by tcp socket and by unix socket.

# by tcp socket
redis://<user>:<password>@<host>:<port>

# by unix socket
unix://<user>:<password>@</path/to/pika.sock

Needs only address, here is an example with two jobs:

jobs:
- name: local
address: 'redis://@127.0.0.1:6379'

- name: remote
address: 'redis://user:[email protected]:6379'

For all available options, see the pika collector's configuration file.

Troubleshooting

To troubleshoot issues with the pika collector, run the go.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working. ' First, navigate to your plugins' directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the setting plugins directory. Once you're in the plugin's directory, switch to the netdata user.

cd /usr/libexec/netdata/plugins.d/
sudo -u netdata -s

You can now run the go.d.plugin to debug the collector:

./go.d.plugin -d -m pika

Was this page helpful?

Contribute