An engine’s health and metrics are what its own detail page shows: power state, catalog sync status, configuration drift, and resource metrics where the console exposes them. Open an engine from the list to see its detail page — there’s no separate “Health” tab; everything below lives on this one page.

Power

State (Ready, Starting, Suspended, Parked, and so on, live), idle-suspend policy, when it last saw a query, and its endpoint once provisioning has published one. See Power and scale to zero.

Catalogs

The catalog sync badge (matching the list’s Configuration column), the list of catalogs currently mounted with their kind, and when the set was last applied. See Catalogs and Apply.

Configuration

The engine’s actual stored tunables, key by key, plus when the platform last checked whether they still match what it would set today. If that check has never run, the page says so rather than implying everything is fine. If it found a mismatch, a banner explains that the platform changed underneath the engine (an upgrade, or a plane-wide setting) and points you to Apply.

Metrics

Why can’t I see CPU, memory or query-count metrics for my engine?

Dippr already gathers this data, but no page in the console shows it yet — there’s no chart, no metrics tab, and no per-node breakdown anywhere in the query engines section. If you need that data today, it isn’t available through the console.

Power and scale to zero

What each power state means and how an engine moves between them.

Catalogs and Apply

What the catalog sync badge and the drift banner are telling you.