automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Using the monitoring stack
- Health endpoints
- Cluster administration
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups

Automation Suite on EKS/AKS installation guide
Last updated Oct 15, 2025
To effectively monitor the health of your Automation Suite services, you can use the health endpoints available in this section. These endpoints allow you to quickly verify if a service is operating correctly.
The following table lists the Automation Suite products and services and their respective health endpoints.
Service | Health endpoint(s) |
---|---|
Platform |
|
Action Center |
|
AI Center |
|
Apps |
|
Automation Hub |
|
Data Service |
|
Document Understanding |
|
Insights |
|
Notification Service |
|
Orchestrator |
|
Robotube |
|
Studio Governance |
|
Studio Web |
|
Task Mining |
|
Test Manager |
|
To check the health of a specific service, send a request to its corresponding endpoint, as show in the following example.
curl -kiso /dev/null -w "%{http_code}" https://<automation-suite-fqdn>/orchestrator_/api/health
curl -kiso /dev/null -w "%{http_code}" https://<automation-suite-fqdn>/orchestrator_/api/health
A successful response with an HTTP status code 200 indicates that the service is healthy.