F Forge DocsRepository ↗FeaturesUser manual

Operations / user manual

Monitoring

Tracks platform and node health. Reads health observations and monitoring integrations.

Purpose

Observe the control plane, understand changes, and coordinate safe work.

ARCHITECTURE

Control-plane observation flow

Forge control plane

01Administratorreview
02Forge Webquery
03Forge APIdurable state
04PostgreSQLhealth and activity
05Beacon observations
API readinessnode heartbeatrecorded activity

How to use it

Operator workflow

  1. 01

    Open Monitoring from the administrator panel and review the current state.

  2. 02

    Set the specific configuration that expresses the desired monitoring outcome.

  3. 03

    Save deliberately, then follow the operation, activity, health, or runtime observation that confirms the result.

  4. 04

    Keep the before-and-after evidence in Activity and verify the workload path before relying on the change.

What Forge owns

Boundary and safety

Operations reads durable state and node observations. It does not give a node independent authority to schedule work.

Use deliberate changes

Review the affected node, workload, route, or secret before saving. Capture state and health evidence before changes that affect data or public traffic.

Before you finish

Verification checklist

  • The operator has the required administrative role.
  • The intended node, workload, or project is selected.
  • The resulting operation or observation reaches a terminal state.
  • A rollback path exists before changing production traffic or storage.

Continue the manual

Use this feature in the wider Forge workflow.

Move from platform understanding to the relevant operating guide when you need exact environment, network, deployment, or recovery steps.