automation-suite
2024.10
true
- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Configuring NLog
Automation Suite on EKS/AKS Installation Guide
Last updated Nov 21, 2024
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
--is-external-storage
parameter.
The
uipathctl
commands needed for updating the NLog configuration are:
uipathctl config orchestrator get-config --nlog-config
- This exports the current configuration in a key-value pair json file, ready for editing.You can read more about it .
uipathctl config orchestrator update-config --nlog-config nlog.config.json
- This updates the configuration with your changes.You can read more about it .