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.

Note:

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.

Generating the support bundle

To generate the support bundle, run the following command:

./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
--output-dir string	Specify the directory to store the support bundle.
--skip-diagnose	Boolean flag to skip the diagnostics report. By default, the bundle contains the diagnostics reports. You can use this flag to exclude the diagnostics report from the support bundle.
--namespace string	Specify the namespace where UiPath Automation Suite is deployed.
--include string	Specify additional components (comma separated) to include in the bundle (such as --include=historical-logs).
--exclude string	Specify components (comma separated) to exclude from the bundle (such as--exclude=rke2-bundle).
--from YYYY-MM-DD	The start date to collect the historical logs in YYYY-MM-DD format.
--days int	The number of days from the start date for which to collect the historical logs.
--limit-bytes int	Limits the size of the logs of running pods by providing the integer value in bytes.

Note:

• 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.

Automation Suite Support Bundle Structure

The .tar.gz archive contains following files and folders:

File/folder	Description
current-logs	Contains the live logs (such as logs for current and previous instance of pods).
events.json	Contains the event descriptions from all the namespaces.
alerts	Contains the active prometheus alerts in the cluster.
namespace/resource/object.yaml	Contains the object descriptions for the server-preferred/custom namespace and cluster-scoped resources.

Note:

Historical logs are not supported in EKS/AKS environments.