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
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version
Configuring NLog

Automation Suite on EKS/AKS installation guide
Last updated Jun 26, 2025
Configuring NLog
Orchestrator loads the following extensions by default, so you do not need to include them in the folder or the NLog configuration:
-
NLog.Targets.ElasticSearch
-
UiPath.Orchestrator.Logs.Elasticsearch
-
Microsoft.ApplicationInsights.NLogTarget
-
NLog.Extensions.AzureEventHub
Only Linux-compatible extensions can be used in this setup, so make sure that your chosen NLog extension abides by this rule.
To make the extension available for use, it must uploaded to the cluster storage.
The
uipathctl
command line tool can do this via the uipathctl config orchestrator upload
command:
uipathctl config orchestrator upload --nlog-extensions-directory /path/to/extensions/directory
uipathctl config orchestrator upload --nlog-extensions-directory /path/to/extensions/directory
If you use an external storage configuration at the cluster level, you must indicate this by including the
--use-external-storage
parameter.