Overview
Capture RiakCS metrics in Datadog to:
- Visualize key RiakCS metrics.
- Correlate RiakCS performance with the rest of your applications.
Minimum Agent version: 6.0.0
Setup
Installation
The RiakCS check is included in the Datadog Agent package, so you don’t need to install anything else on your RiakCS nodes.
Configuration
Edit the riakcs.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory. See the sample riakcs.d/conf.yaml for all available configuration options:
init_config:
instances:
## @param access_id - string - required
## Enter you RiakCS access key.
#
- access_id: "<ACCESS_KEY>"
## @param access_secret - string - required
## Enter the corresponding RiakCS access secret.
#
access_secret: "<ACCESS_SECRET>"
Restart the Agent.
Validation
Run the Agent’s status subcommand and look for riakcs under the Checks section.
Data Collected
Metrics
| |
|---|
riakcs.block_delete.latency_mean
(gauge) | Mean latency of BLOCK DELETE operations performed
Shown as microsecond |
riakcs.block_delete.meter_rate
(gauge) | Rate of BLOCK DELETE operations performed
Shown as operation |
riakcs.block_get.latency_mean
(gauge) | Mean latency of BLOCK GET operations performed
Shown as microsecond |
riakcs.block_get.meter_rate
(gauge) | Rate of BLOCK GET operations performed
Shown as operation |
riakcs.block_put.latency_mean
(gauge) | Mean latency of BLOCK PUT operations performed
Shown as microsecond |
riakcs.block_put.meter_rate
(gauge) | Rate of BLOCK PUT operations performed
Shown as operation |
riakcs.bucket_create.latency_mean
(gauge) | Mean latency of BUCKET CREATE operations performed
Shown as microsecond |
riakcs.bucket_create.meter_rate
(gauge) | Rate of BUCKET CREATE operations performed
Shown as operation |
riakcs.bucket_delete.latency_mean
(gauge) | Mean latency of BUCKET DELETE operations performed
Shown as microsecond |
riakcs.bucket_delete.meter_rate
(gauge) | Rate of BUCKET DELETE operations performed
Shown as operation |
riakcs.object_delete.latency_mean
(gauge) | Mean latency of DELETE operations performed
Shown as microsecond |
riakcs.object_delete.meter_rate
(gauge) | Rate of DELETE operations performed
Shown as operation |
riakcs.object_get.latency_mean
(gauge) | Mean latency of GET operations performed
Shown as microsecond |
riakcs.object_get.meter_rate
(gauge) | Rate of GET operations performed
Shown as operation |
riakcs.object_put.latency_mean
(gauge) | Mean latency of PUT operations performed
Shown as microsecond |
riakcs.object_put.meter_rate
(gauge) | Rate of PUT operations performed
Shown as operation |
riakcs.service_get_buckets.latency_mean
(gauge) | Mean latency of GET BUCKETS operations performed
Shown as microsecond |
riakcs.service_get_buckets.meter_rate
(gauge) | Rate of GET BUCKETS operations performed
Shown as operation |
For RiakCS v2.1+, the default metrics collected by this integrations includes most S3 API metrics as well as memory stats. Some have been excluded:
- bucketacl(get|put)
- objectacl(get|put)
- bucketpolicy(get|put|delete)
- in(one|total)
- time_error*
- _time_100
Any of the excluded metrics or additional metrics (1000+) can be added to the riakcs.d/conf.yaml configuration file with the metrics key in the instance_config. The value should be a list of metric names.
See the complete list of available metrics.
Events
The RiakCS check does not include any events.
Service Checks
riakcs.can_connect
Returns CRITICAL if the Agent is unable to connect to the monitored KyotoTycoon instance. Returns OK otherwise.
Statuses: ok, critical
Troubleshooting
Need help? Contact Datadog support.
Further Reading
Additional helpful documentation, links, and articles:
