automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding application logs to external tools
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
Forwarding application logs to external tools

Automation Suite on EKS/AKS installation guide
Last updated Mar 10, 2025
Forwarding application logs to external tools
You can forward application logs to external tools, such as Splunk, using the OpenTelemetry Collector. For details on how to install and use the OpenTelemetry Collector, refer to the official documentation of the tool provider (such as Splunk official documentation).
This method refers to forwading logs from infrastructure and application pods. For saving robot logs, please refer to Saving robot logs to Elasticsearch.
Note:
For details on how to forward logs to Splunk in versions prior to Automation Suite 2023.10.7, see the How to section.