Metrics

Mission Control collects metrics across all components and aggregates them across projects and clusters. Review this unified observability data in the centralized user interface. Mission Control installs and configures metrics components at the same time as the Mission Control Control Plane and scales those components independently:

These components enable you to monitor metrics from many sources within Mission Control, including:

  • Platform services

  • Operators

  • Observability components

  • Reaper

  • Database instances

Mission Control only deploys observability components to Platform instances.

The metric refresh interval is configured by the Vector Aggregator scraping system. Metrics are read from the database as the scraping occurs, providing the most up-to-date metrics.

See collected metrics with Mission Control’s graphical metrics view.

Prerequisites

You must provide an AWS S3 or S3-compatible, Google Cloud Storage, or an Azure Blob Storage object store during installation and configuration. All metrics are stored within an object store, providing long-term storage for metrics.

When storing metrics in the cloud is a concern, for instance if a cloud provider isn’t used, an S3 API can be used to store objects. For companies that do not have an S3 endpoint, it is possible to use MinIO to provide an S3-compatible object store within the Mission Control platform.

Mission Control makes it easy to push metrics to existing monitoring stacks. Manipulate and send observability data externally by adding custom transforms and sinks in the Mission Control configuration.

Access metrics

Use Mission Control UI to access metrics.

  1. Access Mission Control’s UI.

  2. In the Home Clusters dialog, click the target cluster namespace.

  3. Click the Observability tab.

  4. In the Health Metrics tab, choose one of the view’s dialogs and hover on any part of the chart to see detailed information. Review details for a specific time by moving your cursor along the horizontal time line.

  5. Optional: In the Filter field, select the datacenter to monitor.

  6. Optional: In the Frequency field, select the duration in which to refresh the metrics.

  7. Optional: In the Time Period field, select the monitoring time period.

What metrics can I see?

Various Mission Control views reveal real-time and historical performance status about clusters, datacenters, nodes, tables, data, and storage tiers.

  • Overview view

  • Node view

  • Observability view

  1. Access Mission Control’s UI.

  2. In the Home Clusters dialog, click the target cluster namespace.

  3. In the Overview tab, the Mission Control Overview view reveals datacenter and node information.

  1. Access Mission Control’s UI.

  2. In the Home Clusters dialog, click the target cluster namespace.

  3. In the Nodes section of the Overview tab, in the Name column, click on a node.

  4. Monitor node specifics such as:

    • Availabilty of nodes - the status is right next to the node name

    • Type of database - Cassandra or DSE

    • Storage Capacity - largely measured in gigabytes (GB)

    • Load

    • Memory Usage - with details about System, Heap, and In Memory usage

    • Gossip activity

    • Pending Tasks

    • Number of Native clients

    • Days of Uptime

    • Running Tasks - with Type, SSTable, and Progress

    • Incoming Streams - with Operation, Peer, and Progress

    • Outgoing Streams - with Operation, Peer, and Progress

    • Thread Pool Stats - with Name, Active, Pending, Completed, Blocked, and Total Blocked

  1. Access Mission Control’s UI.

  2. In the Home Clusters dialog, click the target cluster namespace.

  3. Click the Observability tab.

  4. In the Examine metrics and logs window, monitor datacenter activity in the cluster for a specific Frequency and Time Period:

    • Read/Write Throughput

    • Read/Write Latencies

    • Other Latencies

    • Errors

    • CPU Utilization

    • Unix Load

    • Garbage Collection Time

    • Disk Read Throughput

    • Disk Write Throughput

    • Network IO - with Receive (RX) and Transmit (TX) values

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