Before you begin
Confirm account, tenant and active role in the account menu. Inspection requires view permission; changing records requires the specific management permission. A hidden or disabled action can reflect authorized scope; do not switch tenants to evade a denial. Work only with records in the workspace you are allowed to administer.
Procedure
- Open Overview and inspect Tenants, Users, Subscriptions, Invoices, Usage and Security.
- Select a worker and a 1h, 6h or 24h interval to compare CPU, memory and disk.
- Open the relevant module to investigate its underlying record.
Behavior and limits
Administrator has ten primary modules; the sixteen chapters in this manual also cover specialized procedures. Charts represent available observations and actions depend on the active role.
A card does not prove payment, execution success or guaranteed capacity. An absent measurement or a failed load is not zero.
Compare samples for the same worker and period. Inspect measurement coverage before attributing a change to a pipeline. Zoom controls change the visible range; Refresh requests current observations.
Verify the result
After saving or confirming, reopen the detail and check the state reported by the server. Distinguish an accepted request from a completed operation and retain only minimal evidence without sensitive information. When an operation is pending, wait for its final state in the corresponding view before starting another action on the same object.
Laboratory example
Use the synthetic tenant documentation-lab and, where relevant, worker worker-demo-a. Note the previous state, perform one authorized action and compare the resulting state. These names illustrate the procedure; they do not identify production records or authorize creating cloud resources. For a review without changes, inspect the detail and cancel any open form.
If something fails
If a conflict appears, refresh the inventory and review current values before repeating. If the session expired, sign in and complete MFA when required. For a permission error, check the role and membership; for a provider error, inspect the operation and its safe message. Do not alter storage, revisions or controls to force an outcome.
Related reading
Continuous updates and stable reading
Overview checks for changes every five seconds while the view is active. Charts and cards retain their structure and previous data while a response arrives; selection, range, zoom and scroll are preserved. Live shows the last confirmed update. Last confirmed and Refresh pending indicate that the read could not be renewed: visible values remain the last observation, not a new measurement.
The screen refresh interval does not change telemetry sampling frequency. A missing sample is shown as unknown rather than converted to zero. Selection controls and legends retain their position while values update.
Dova base server
Platform administrators see vm-cloudata-pe labeled Base server. It is the server hosting Dova and remains in Overview even when samples are missing or its state cannot be confirmed. It is excluded from execution worker counts and has no removal action in this view.
Metrics come from local host sampling when its identity can be verified; they do not replace a GCP state query. If identity or measurements are unavailable, the row remains and displays unknown information rather than attributing another host's activity to it.
Fast Administrator reads
Administrator loads authorized module or tab data when needed and briefly reuses reads in RAM with size and expiry limits. Identical overlapping reads are joined; changes to data, identity, role or context invalidate the corresponding reuse. An earlier context’s response does not replace the current view. Periodic updates preserve selection and visible state while data remains valid. These measures reduce repeated reads; actual timing depends on data, network and provider.
Grid row updates preserve open menus, filters, selection and scroll. When an action starts, its control shows In progress and other actions in that grid are blocked until its result; other modules and reading controls remain available.
Navigation shared with Dova
Dova and Administrator share the left sidebar’s presentation and behavior: text, active and hover states, keyboard focus, collapse and user alignment. The user menu opens beside its button and remains within the screen. Available modules and actions still depend on your permissions.
Read CPU, memory and disk
CPU, Memory and Disk show Not available when there is no valid current measurement, the VM is unavailable or heartbeat/provider observation has expired. An unavailable reading is not zero. Earlier history may remain with Historical or Last recorded and its timestamp; do not treat it as current usage.
Available disk represents free space. Review Capacity, Used and the percentage to understand occupied space. The vertical axis starts at zero and uses known capacity for scale; the horizontal axis uses the displayed local time. Hover, focus and keyboard reveal the exact sample and, when capacity is known, used and total values. Last sample and timezone identify when the data was observed.
The Dova base server row identifies the platform host and remains protected. Its local telemetry is used only after identity verification; those readings do not by themselves confirm native cloud VM state.