Use the iagctl inspect cluster commands to monitor the live state of a gateway cluster. These commands give you visibility into cluster health and active execution before you perform maintenance tasks like taking a runner node offline, restarting a service, or making configuration changes.
To view gateway cluster details, admin state, certificates, and service groups in the Gateway Manager UI, see View gateway cluster details.
Cluster health and activity can also be checked directly from a workflow using the Inspect Cluster task from the GatewayManager collection in the task palette. For more information on adding tasks to workflows, see Create and run workflows.
Run iagctl inspect cluster health to verify that the gateway cluster’s backing datastore is reachable and that at least one runner node is responding. Use this command before performing maintenance to confirm the gateway cluster is in a known good state, or after a change to verify the cluster recovered as expected.
The command checks the following:
The command exits with code 0 when the cluster is healthy and a non-zero code when unhealthy, with no output parsing required.
Example output:
For full output field descriptions, see iagctl inspect cluster health.
Run iagctl inspect cluster activity to see all currently running and recently completed work across every runner node in the cluster. Use this command to confirm that no services are actively executing before taking a runner node offline or restarting the gateway cluster.
The command fans out to all registered runners simultaneously and returns a combined view of execution activity.
Example output:
Recently completed work is retained in the activity output for up to 15 minutes after completion. After that window, entries no longer appear.
For full output field descriptions, see iagctl inspect cluster activity.
Run iagctl inspect cluster without a subcommand to display health and activity output together in a single call.
For more information, see iagctl inspect cluster.