- 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
- Service alerts
- Health endpoints
- Cluster administration
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Service alerts
This alert indicates that one of the services is not accessible because none of the PODs operating that service is in good health.
If this alert fires, take the following steps:
-
Generate the support bundle. For details, see Using the Automation Suite support bundle.
-
For troubleshooting, refer to this section.
-
If you still face issues, contact UiPath® Support with the generated support bundle in step 1.
This alert indicates that one of the services is not accessible because one or more PODs running that service is/are not healthy.
If this alert fires, take the following steps:
-
Generate the support bundle. For details, see Using the Automation Suite support bundle.
-
For troubleshooting, refer to this section.
-
If you still face issues, contact UiPath® Support with the generated support bundle in step 1.
