Monitor Your Kubernetes Cluster
On this page
Overview
SingleStore’s native monitoring solution is designed to capture and reveal SingleStoreDB cluster events over time.
Terminology
Throughout this guide, the cluster that is being monitored is referred to as the Source
cluster, and the cluster that stores the monitoring data is referred to as the Metrics
cluster.metrics
database.
High-Level Architecture

In SingleStore’s native monitoring solution, the Metrics cluster utilizes a SingleStore pipeline to pull the data from the exporter process on the Source cluster and store it in a database named metrics
.metrics
database can either reside within the same cluster as the Source cluster, or within a dedicated cluster.
When these event data is then analyzed through the provided Grafana dashboards, trends can be identified and, if necessary, actions taken to remediate issues.
The provided Grafana dashboards include:
Dashboard |
Description |
---|---|
Cluster View |
Provides a “bird's-eye view” of a single SingleStoreDB cluster. |
Detailed Cluster View by Node |
Provides a view into resource utilization by node. |
Historical Workload Monitoring |
Statistics for parameterized query execution including run count, time spent, and resource utilization. |
Memory Usage |
Granular breakdown of memory use for a node. |
Prerequisites
-
A SingleStoreDB 7.
3 or later cluster deployed via Kubernetes Operator to monitor (the Source cluster) -
Optional: A separate SingleStoreDB 7.
3 or later cluster deployed via a Kubernetes Operator used to collect monitoring data (the Metrics cluster)
Monitoring License
If the size of the cluster that is hosting the monitoring data is 4 units or under, it can use a free tier license.
In this section
Last modified: March 31, 2023