Riak is an open source, distributed database. It offers high availability, fault tolerance, operational simplicity, and scalability. For more information, visit the Riak GitHub repository.
Discovery
Even if the Riak plugin is not configured, Stackdriver Monitoring will discover Riak services running in your Cloud Platform project by:
- searching instance names for riak
- checking for ports opened to 8098 via firewall rules
The services discovered are displayed on the Riak Services page in the Resources menu. After you install the monitoring agent and configure the Riak plugin on your instances, Stackdriver Monitoring populates the Riak Services page with inventory and metrics.
Configuring Stackdriver Monitoring to monitor Riak
After you install the monitoring agent, use the following instructions to configure the Riak plugin on your instances.
Prerequisites
The Riak plugin requires version 5.5.0-315 or later of the monitoring agent. To update the agent, see Upgrading the agent.
Enabling the Riak monitoring plugin
On your VM instance, download riak.conf from the
GitHub configuration repository
and place it in the directory /opt/stackdriver/collectd/etc/collectd.d/:
(cd /opt/stackdriver/collectd/etc/collectd.d/ && curl -O https://raw.githubusercontent.com/Stackdriver/stackdriver-agent-service-configs/master/etc/collectd.d/riak.conf)
After adding the configuration file, restart the monitoring agent by running the following command:
sudo service stackdriver-agent restart
Information on other plugin configuration options can be found at collectd.org.
What is monitored
The Riak plugin monitors the following metrics:
- Node Operations (count/s): How many Get and Put operations take place on the node.
- VNode Operations (count/s): How many Get, Put, Index Read/Write/Delete/DeletePostings take place on the VNode.
- Memory Usage: Various memory statistics from the Erlang process that riak is running within.
- Coordinated Redirects (count/s): How many coordinated redirects took place on this server.
- Read Repairs (count/s): How many read repairs took place on this server.
- FSM Object Size: Mean, 95th Percentile, and Maximum object sizes in the Finite State Machine.
- FSM Siblings: Mean, 95th Percentile, and Maximum sibling calls in the Finite State Machine.
- FSM Get Latency: Mean, 95th Percentile, and Maximum get latency in microseconds.
- FSM Put Latency: Mean, 95th Percentile, and Maximum put latency in microseconds.
