Skip to main content


Plugin: python.d.plugin Module: rethinkdbs


This collector monitors metrics about RethinkDB clusters and database servers.

It uses the rethinkdb python module to connect to a RethinkDB server instance and gather statistics.

This collector is supported on all platforms.

This collector supports collecting metrics from multiple instances of this integration, including remote instances.

Default Behavior


When no configuration file is found, the collector tries to connect to


The default configuration for this integration does not impose any limits on data collection.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.


Metrics grouped by scope.

The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

Per RethinkDB instance

These metrics refer to the entire monitored application.

This scope has no labels.


rethinkdb.cluster_connected_serversconnected, missingservers
rethinkdb.cluster_documentsreads, writesdocuments/s

Per database server

This scope has no labels.


rethinkdb.documentsreads, writesdocuments/s


There are no alerts configured by default for this integration.



Required python module

The collector requires the rethinkdb python module to be installed.



The configuration file name for this integration is python.d/rethinkdbs.conf.

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config python.d/rethinkdbs.conf


There are 2 sections:

  • Global variables
  • One or more JOBS that can define multiple different instances to monitor.

The following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.

Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition.

Every configuration JOB starts with a job_name value which will appear in the dashboard, unless a name parameter is specified.

Config options
update_everySets the default data collection frequency.5no
priorityControls the order of charts at the netdata dashboard.60000no
autodetection_retrySets the job re-check interval in seconds.0no
penaltyIndicates whether to apply penalty to update_every in case of failures.yesno
nameJob name. This value will overwrite the job_name value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that
hostHostname or ip of the RethinkDB server.localhostno
portPort to connect to the RethinkDB server.28015no
userThe username to use to connect to the RethinkDB server.adminno
passwordThe password to use to connect to the RethinkDB
timeoutSet a connect timeout to the RethinkDB server.2no


Local RethinkDB server

An example of a configuration for a local RethinkDB server

name: 'local'
host: ''
port: 28015
user: "user"
password: "pass"


Debug Mode

To troubleshoot issues with the rethinkdbs collector, run the python.d.plugin with the debug option enabled. The output should give you clues as to why the collector isn't working.

  • Navigate to the plugins.d directory, usually at /usr/libexec/netdata/plugins.d/. If that's not the case on your system, open netdata.conf and look for the plugins setting under [directories].

    cd /usr/libexec/netdata/plugins.d/
  • Switch to the netdata user.

    sudo -u netdata -s
  • Run the python.d.plugin to debug the collector:

    ./python.d.plugin rethinkdbs debug trace

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.