Overview
Command Center provides a unified operations platform for your Crusoe GPU clusters, replacing fragmented monitoring tools with centralized observability, automated alerting, and integrated support workflows.
Why Command Center
Large-scale AI workloads require visibility into every resource in your cluster. Command Center delivers real-time telemetry across your infrastructure, eliminating the need for you to switch between SSH sessions, log dumps, and third-party dashboards.
Key Capabilities
- Infrastructure Overview — See a project-level fleet summary grouped by instance type, with GPU utilization, health status, and drill-down to cluster or VM details.
- View cluster topology — See health and utilization of every node, arranged by network topology.
- Monitor metrics — Track GPU, CPU, memory, storage, and network performance. Ingest custom application metrics.
- Access logs — Query JournalD system logs without SSH.
- Export telemetry — Export metrics to Grafana, Datadog, or Splunk via Prometheus-compatible endpoints.
- Receive alerts — Get notified about hardware failures and cluster events via email, Slack, or webhooks.
Components
Command Center consists of the following components:
| Component | Description | Availability |
|---|---|---|
| Infrastructure and Topology Overview | Project-level fleet summary grouped by instance type with health and GPU utilization, plus visual cluster topology with node health overlays | CMK and VM (CWA required); topology view: CMK only |
| Metrics | Infrastructure and custom application metrics with Prometheus-compatible API and Crusoe Cloud Console | CMK and VM (custom metrics: CMK only) |
| Logs | Managed log collection and search for Kubernetes and system logs | CMK and VM |
| Instance Health | Healthy, Degraded, or Unhealthy status for CMK nodes and standalone VMs, derived from GPU telemetry and lifecycle events | CMK and VM (CWA required) |
| Alerts | Get notified about hardware failures and cluster events via email, Slack, or webhooks | CMK and VM |
| Telemetry Conduit | Export infrastructure metrics to external observability platforms | CMK and VM |
| Natural Language Query | Query infrastructure metrics and logs in plain English via Crusoe MCP | CMK and VM (see Crusoe MCP) |
Prerequisites
To use Command Center, you need:
- Crusoe Cloud account with an active project
- Crusoe CLI installed and configured
kubectlconfigured with cluster access if you are a CMK userhelminstalled if you are a CMK user
Get Started
Command Center requires the Crusoe Watch Agent to collect telemetry from your infrastructure. For installation instructions, token generation, and access method details, see Get Started.
Integration with Crusoe Services
Command Center integrates with AutoClusters for automated hardware failure detection and node replacement for CMK clusters. Remediation events appear in Notification Center.
For GPU XID error alerts on standalone VMs and CMK nodes, see Notifications.
What's Next
- Infrastructure and Topology Overview — View fleet-level health and utilization, and drill into cluster topology
- Instance Health — Understand health status categories and error codes
- Metrics — Configure and query infrastructure and custom metrics
- Logs — Search and filter Kubernetes and system logs
- Telemetry Conduit — Export metrics to external platforms
- Notification — Get notified about resource health via email and in-console, and set up alert routing to Slack or webhooks