Migrating UiPath Orchestrator from an on-premises deployment to Automation Cloud simplifies infrastructure management, but it also changes how execution logs can be accessed and consumed. Teams migrating existing Splunk-based observability pipelines often discover that familiar on-prem logging patterns no longer apply once workloads move to the cloud.

In on-prem environments, Orchestrator and robot logs are typically available as files on the server filesystem, making them easy to ingest into centralized monitoring platforms using standard forwarders. Automation Cloud removes direct access to the underlying infrastructure, forcing teams to rethink how logging should be handled after migration.