GridGain Developers Hub

GridGain Control Center Overview

GridGain Control Center is a management and monitoring tool for GridGain® and Apache Ignite® clusters. It features a graphical user interface that helps you perform administrative tasks and monitor your clusters.

Control Center on-premise provides most of the benefits of Control Center SaaS in your own environment.

With Control Center on-premise running in your closed network you do not risk exposing your clusters internet-wide, and can provide as much or as little hardware as necessary for it to run. You also get access to configuration parameters and command-line options that can fine-tune Control Center to suit your specific needs.

To get a GridGain Control Center license, contact our sales team. If you do not want to run Control Center locally, try GridGain Nebula to monitor your clusters instead.

Key Features

  • Monitor performance metrics: A flexible, customizable dashboard provides a visual view of cluster status and tools for managing cluster behavior.

  • Simplify query development: A comprehensive SQL editor makes it easy to develop, monitor, and fine-tune queries to maximize performance.

  • Perform powerful root-cause analysis: OpenCensus-based tracing enables quick visualization and debugging of API calls as the calls execute across the nodes of the cluster.

  • Back up and recover data: Snapshots capture full, incremental, and continuous cluster states to enable disaster recovery and backups in the event of data loss or corruption.

  • Define Production Alerts: Custom alerts enable you to track any of more than 200 cluster, node, and cache metrics to quickly identify and resolve production issues.

Supported GridGain and Apache Ignite Versions

You can use Control Center to monitor both GridGain and Apache Ignite clusters. Some Control Center features become available in specific versions depending on GridGain or Apache Ignite version:

Feature GridGain Version Apache Ignite Version

Distributed Computing



Code Deployment



Persistent Dashboard Templates



Running queries



Log collection



Thread dump collection



Triggering garbage collector on node



Data center replication dashboards

8.8.37+; 8.9.1+

Scan queries

8.8.37+; 8.9.1+

Binary Type Management

8.8.36+; 8.9.1+

Version Lifecycle

Public Version Supported GridGain Versions First Public Release Date End-Of-Life Date


GridGain 8.8.1+, Apache Ignite 2.8.1+

February 2022

February 2024


GridGain 8.8.1+, Apache Ignite 2.8.1+

August 2022

August 2024


GridGain 8.8.1+, Apache Ignite 2.8.1+

October 2022

October 2024


Control Center licenses for the number of nodes you run in your clusters, and can monitor these clusters for the duration. To get a Control Center license, contact us.

System Requirements

Control Center system requirements scale depending on the size of the cluster monitors, as well as the number of metrics it gathers. This section describes system requirements for a Control Center working with a small 4 or 10-node cluster, gathering most of the important metrics. When deploying Control Center to monitor production environments, requirements for storage, RAM and CPU will be higher.


Latest available version of Firefox, Safari, and Google Chrome. Browsers based on the latest Chromium version.


Linux (any flavor), Mac OSX (10.6 and up), Windows (XP and up), Windows Server (2008 and up). For Docker environment, we provide Linux docker containers.


Oracle JDK 11 or 17, Open JDK 11 or 17, IBM JDK 11 or 17.


Required storage space strongly corresponds to the size of the cluster and the number of metrics, traces, and compute tasks. Here are some examples:

  • 10 GB for a 4-node cluster.

  • 20 GB for a 10-node cluster.

The examples above assume default configurations for Control Center with 1 week TTL on gathered metrics and storage left for traces and compute tasks data.


8 GB minimum, 16 GB is recommended.


4 cores minimum, 8 cores recommended.


x86-64 platform.

Currently, Control Center memory use is limited in following ways:

  • 2 GB for heap memory;

  • 2 GB for off-heap memory;

  • Direct buffers memory is not limited. To limit it, use the following command:


Next Steps

A standard procedure for connecting a cluster to Control Center involves the following steps: