Console Status Operations
The Console Status page sends an authenticated GET request to:
/api/console-backend/status/
While the page is open and the browser tab is focused, Console repeats the request approximately every two seconds. The backend runs the checks below for each request and returns one combined response. For a description of the fields displayed in Console, see Console Status.
Operations
| Check | Operation | Expected Result |
|---|---|---|
| Database | Runs SELECT 1 using the configured Console database connection. | The query returns a row. |
| Kubernetes | Loads the Kubernetes configuration, creates a Core API client, and requests the API resource list. | The configuration loads and the Kubernetes API responds. |
| Deployments | Reads the deployments.smoothglue.io CRD when deployments are enabled. | The CRD exists. |
| DataMesh | Reads the xdatameshes.smoothglue.io CRD when Data Mesh is enabled. | The CRD exists. |
| Origins | Reads the xpublications.cdc.datamesh.smoothglue.io CRD when Data Mesh is enabled. | The CRD exists. |
| Destinations | Reads the xsubscriptions.cdc.datamesh.smoothglue.io CRD when Data Mesh is enabled. | The CRD exists. |
| Keycloak | Requests a client-credentials token, then sends an authenticated GET request to the realm's Admin API clients endpoint. | A token is returned and the Admin API request succeeds. |
| GitLab | Sends an authenticated GET request to /api/v4/version when GitLab is enabled. | The request succeeds; the response version is included in the check details. |
| Jira | Sends an authenticated GET request to /rest/api/2/serverInfo when Jira is enabled. | The request succeeds; the response version is included in the check details. |
| Mattermost | Sends an authenticated GET request to /api/v4/users/me when Mattermost is enabled. | The request succeeds; when available, the X-Version-Id response header supplies the displayed major, minor, and patch version. |
| Prometheus | Sends GET /api/v1/query?query=up when Data Mesh metrics are enabled. | The HTTP request succeeds and the response contains status: "success". |
| Platform version | Reads the cluster-scoped structsure-enterprise Crossplane configuration and extracts the image tag from spec.package. | The package contains a tag such as v6.19.1. This lookup does not affect the health summary. |
Optional checks return not_applicable when their related feature or integration is disabled. They
are not included in the summary counts. For more information about configuring the services, see
Integrations Reference.
Response Shape
A successful status operation returns HTTP 200, including when one or more checks are unhealthy.
Each check contains a status, a human-readable message, and a details object.
The overall status is calculated from applicable checks:
| Status | Result |
|---|---|
healthy | No applicable checks are unhealthy. |
degraded | At least one applicable check is healthy and at least one is unhealthy. |
unhealthy | All applicable checks are unhealthy. |
Failure Cases
| Condition | Result |
|---|---|
| The API request is not authenticated. | The endpoint returns HTTP 401 or 403 without running the checks. |
| A feature or optional integration is disabled. | The check is not_applicable and is excluded from the summary. |
| An enabled service is missing its URL or credentials. | The check is unhealthy with configured: false. No request is sent to that service. |
| A database, Kubernetes, or service request fails or times out. | The affected check is unhealthy with a safe, generic message. Other checks continue to run. |
A required CRD returns 404. | The check is unhealthy with present: false. |
| Prometheus responds successfully but reports a non-success query status. | The Prometheus check is unhealthy. |
| The platform version resource is missing, unreadable, or has an unexpected package value. | platform_version is Unknown; health counts are unchanged. |
| The combined status operation cannot complete. | The endpoint returns HTTP 500 with error and details fields, and the page displays Failed to load system status. |
The API endpoint is available to authenticated users. Platform Admins can also receive safe
diagnostic fields such as error_type and status_code for failed checks. Credentials, tokens,
raw upstream response bodies, and exception messages are redacted from the response.
The Console UI page is available to the Platform Admin role. If you need to investigate a failed check from inside the cluster, see Access the Console Backend Pod.