- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Supported OS
Capture RiakCS metrics in Datadog to:
The RiakCS check is included in the Datadog Agent package, so you don’t need to install anything else on your RiakCS nodes.
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>"
Run the Agent’s status
subcommand and look for riakcs
under the Checks section.
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 |
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.
The RiakCS check does not include any events.
riakcs.can_connect
Returns CRITICAL
if the Agent is unable to connect to the monitored KyotoTycoon instance. Returns OK
otherwise.
Statuses: ok, critical
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: