Components Card
The Components card on the Platform Status page is the at-a-glance health read. Each row is one component, with a colored dot, the component name, and a short state on the right.
| ROW | WHAT IS CHECKED | STATE SHOWN WHEN HEALTHY |
|---|---|---|
| Dataplane | The platform sends a health check to the Dataplane and waits for a reply carrying its configuration and runtime metrics. | The engine type with its logo (Kubernetes, Databricks, or Local). When the engine does not reply, unhealthy appears in red next to it. |
| Database | A lightweight query is run against the platform's primary database. | reachable |
| RabbitMQ | Reachability of the message broker that carries every operation request between the platform and the Dataplane. It is derived from the Dataplane health check round trip, and only probed separately when that round trip fails. | consuming |
Status Indicator
| INDICATOR | MEANING |
|---|---|
| Green | The component responded and is operating normally. |
| Red | The component did not respond, or reported a failure. |
| Grey | The state is unknown because the status request itself did not return. This is not the same as unhealthy. |
Warning
If the Database row is unhealthy, the platform cannot save or read any data. Sign-in, datastore management, and operation history are all affected.
Warning
If the RabbitMQ row is unhealthy, no operation request can reach the Dataplane, so the Dataplane health check cannot run either and its row will also report unhealthy. Operations stay unavailable until the connection is restored.
Supported Engines
| No. | Engine |
|---|---|
| 1. |  Kubernetes |
| 2. |  Databricks |