You can monitor your existing Automation Orchestrator cluster through the System tab of the Automation Orchestrator Client dashboard.

The recommended method for monitoring the configuration synchronization states of the Automation Orchestrator instances is through the System tab of the Automation Orchestrator Client dashboard.

Note: If you are unable to access the Automation Orchestrator Client dashboard, you can also monitor the states of your Automation Orchestrator instances by running the kubectl get pods -n prelude command from the Automation Orchestrator Appliance command line.
Configuration Synchronization State Description
RUNNING The Automation Orchestrator service is available and can accept requests.
STANDBY The Automation Orchestrator service cannot process requests because:
  • The node is part of a High Availability (HA) cluster and remains in a standby mode until the primary node fails.
  • The service cannot verify the configuration prerequisites, like a valid connection to the database, authentication provider, and the Automation Orchestrator instance license.
Failed to retrieve the service's health status The Automation Orchestrator server service cannot be contacted because it is either stopped or a network issue is present.
Pending restart Control Center detects a configuration change and the Automation Orchestrator server restarts automatically.