Collecting object I/O level diagnostics

The following object I/O level diagnostic tables collect data on object I/O statistics:

  • object_io

    Per node recent latency metrics by keyspace and table.

  • object_read_io_snapshot

    Per node recent latency metrics, broken down by keyspace and table and orders data by mean read latency.

  • object_write_io_snapshot

    Per node recent latency metrics, broken down by keyspace and table and orders data mean write latency.

Procedure

  1. To enable the collection of this data:

  2. Edit the dse.yaml file.

  3. In the dse.yaml file, set the enabled option for resource_level_latency_tracking_options to true.

    resource_level_latency_tracking_options:
        enabled: true
        refresh_rate_ms: 10000
  4. (Optional) To control how often the statistics are refreshed, increase or decrease the refresh_rate_ms option in dse.yaml.

    The refresh_rate_ms specifies the length of the sampling period, that is, the frequency with which this data is updated.

Was this helpful?

Give Feedback

How can we improve the documentation?

© 2024 DataStax | Privacy policy | Terms of use

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: +1 (650) 389-6000, info@datastax.com