- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- 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
- Cluster administration
- Product-specific configuration
- Troubleshooting
- Running the diagnostics tool
- Running the support bundle tool
- Exploring summarized telemetry

Automation Suite on OpenShift installation guide
Running the support bundle tool
The Automation Suite support bundle tool collects application-level logs of UiPath® services and other software components, such as Istio, ArgoCD, etc. The Automation Suite support bundle tool also contains historical records you can use to analyze patterns when troubleshooting a problem. Detailed logs are particularly helpful when the potential root cause of an issue is not evident just by looking at the state of the cluster.
The Automation Suite support bundle tool is also needed when asking for guidance or a fix from the UiPath® Support team as they need it for analysis purposes.
The Automation Suite support bundle tool does not collect or store any PII or confidential data of you, your user, or your automation. UiPath® applications not not leak or log any confidential information in their records. At the platform level, the log collector is designed to mask any such critical information.
High-level summarized usage telemetry is also exported with this tool generating an XML file. This telemetry includes:
-
Robot execution duration per month by robot type.
-
Robot concurrency - the maximum number of robots that executed at the same time.
-
Metrics on jobs run, processes run, queue items, job failure rate, and users.
-
Environment information.
You can upload the XML file in the Customer Portal to share your high-level self-hosted usage telemetry with the UiPath Support team.
service-metrics
in the excluded list in Automation Suite 2024.10 and higher.
To generate the support bundle, run the following command:
./uipathctl health bundle input.json --versions version.json
./uipathctl health bundle input.json --versions version.json
This tool takes some time to gather and store all the logs in a temporary location on your local / management machine.
The following table lists the optional flags the support bundle tool support:
Flags |
Description |
---|---|
|
Specify the directory to store the support bundle. |
|
Specify the namespace where UiPath Automation Suite is deployed. |
|
Specify additional components (comma separated) to include in the bundle (such as
--include=historical-logs ).
|
|
Specify components (comma separated) to exclude from the bundle (such as
).
|
|
The start date to collect the historical logs in YYYY-MM-DD format. |
|
The number of days from the start date for which to collect the historical logs. |
|
Limits the size of the logs of running pods by providing the integer value in bytes. |
-
By default, if the
--from
flag is not specified, then the historical logs will be collected for the past 2 days starting from today, irrespective of the--days
specified. -
If the
--from
is specified and--days
is not specified, then the historical logs will be collected for 2 days starting from the specified start date.
.tar.gz
archive contains following files and folders:
File/folder |
Description |
---|---|
|
Contains the live logs (such as logs for current and previous instance of pods). |
|
Contains the event descriptions from all the namespaces. |
|
Contains the active prometheus alerts in the cluster. |
|
Contains the object descriptions for the server-preferred/custom namespace and cluster-scoped resources. |
service-metrics | Contains high level usage telemetry stored in individual XML files. |