Use the Infra console

Use the Infra console

Navigate fleet inventory, resource details, metrics, and journals.

The Infra console shows infrastructure configuration, observed health, and change history within the selected organization and project.

Scope and navigation

Sign in at the control plane's configured public URL. Use the organization and project selectors in the console header before opening a resource area.

The organization selector changes membership, policy, billing, and fleet scope. The project selector filters application resources. All projects aggregates resources visible to the current account; it does not grant additional access. Creation forms require a specific project.

Use Fleet for owned region inventory and host admission. Use Compute, Storage, and Networking for project workloads and their dependencies. These lists share scope selectors but expose different permission boundaries. A project operator can inspect a droplet without receiving the host's management controls.

Observe contains metric queries, journals, dashboards, and evaluated alerts. Operations contains the accepted work that changes infrastructure, including maintenance plans and migrations. Read an operation to establish execution outcome; use observations to establish current health.

Settings changes access, project policy, audit destinations, and installation configuration according to the account's grants. A saved settings value can still require an asynchronous rollout to consumers.

Search accepts names, immutable resource IDs, and labels. Opening an ID preserves its organization scope. A resource that is outside your permissions is omitted from results. Saved filters retain region, project, labels, and health criteria.

Resource details

A resource header shows its identity, project, region, state, health, and latest observation time. State describes lifecycle; health describes whether the resource is operating as expected. A running droplet can have degraded storage or an unreachable agent.

The Overview tab lists configuration and dependencies. Metrics displays samples for the selected period. Journal contains timestamped component events. Operations lists changes affecting the resource. Audit records who requested those changes.

Select a node's Droplets tab to inspect placement and active migrations. The migration row links to transferred memory, remaining work, destination checks, and the operation journal. A migration's destination is provisional until the operation commits placement.

Freshness and disconnected resources

A live indicator reports whether the console is receiving new observations. When disconnected, the last observation remains visible with its timestamp. Refreshing the browser does not force an unreachable agent to report.

Configuration requests can remain queued while observations are stale. Review operation state before issuing a second action. A chart gap means there is no sample for that interval; it is not a zero value.

Bulk actions

Select rows and choose an available action. The preview lists each target, required permission, blockers, and expected impact. Bulk actions create child operations per resource. One failure does not reverse successful changes to other resources.

Filters define the visible list; selected IDs define the submitted targets. Changing the filter does not automatically select newly matching rows. Refresh the preview after changing labels, quotas, or placement constraints.

Review changes

Actions that stop workloads, detach storage, or delete resources show an impact review. Confirm the target IDs and retained resources. The review is a snapshot; execution checks dependencies again and can reject a target that changed.

Use Common tasks for procedures and Troubleshooting to interpret failed operations.