- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Managing robot logs
You can change the log level via:
-
the Log Level setting in Assistant > Preferences > General page. By default, it is set to Information. For the Service Mode Robot, you need administrator permissions.
-
the Logging Level setting in Orchestrator > Manage Access > Users > user or robot account > Robot Settings page. By default, it is set to Information.
Note:The log level you set in Orchestrator overrides the level configured in Assistant.
NLog.config
file, under the <target>
section, as follows:
-
By adding the properties
archiveNumbering="Date"
andarchiveEvery="Day"
, you instruct the system to archive log files on a daily basis, with each archive named by the date. -
The property
archiveDateFormat="yyyy-MM-dd"
sets the format for the dates in the archive file names. -
With
archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log"
, you specify the location and format for the archived file names. -
The
maxArchiveFiles="10"
property sets a limit to only keep the 10 most recent archived log files.
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" />
<rules>
<logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
</rules>
<targets>
<target type="File"
name="WorkflowLogFiles"
fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log"
layout="${time} ${level} ${message}"
keepFileOpen="true"
openFileCacheTimeout="5"
concurrentWrites="true"
encoding="utf-8"
writeBom="true"
archiveNumbering="Date"
archiveEvery="Day"
archiveDateFormat="yyyy-MM-dd"
archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log"
maxArchiveFiles="10"
/>
</targets>
</nlog>
<?xml version="1.0" encoding="utf-8" ?>
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" />
<rules>
<logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" />
</rules>
<targets>
<target type="File"
name="WorkflowLogFiles"
fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log"
layout="${time} ${level} ${message}"
keepFileOpen="true"
openFileCacheTimeout="5"
concurrentWrites="true"
encoding="utf-8"
writeBom="true"
archiveNumbering="Date"
archiveEvery="Day"
archiveDateFormat="yyyy-MM-dd"
archiveFileName="${WorkflowLoggingDirectory}/{#}_Execution.log"
maxArchiveFiles="10"
/>
</targets>
</nlog>
UiPath.Executor.exe.config
file. Add the following XML snippet under the <system.serviceModel>
section, then restart the Robot Service:
<tracking>
<profiles>
<trackingProfile name="StandardProfile">
<workflow>
<activityStateQueries>
<activityStateQuery activityName="*">
<states>
<state name="Faulted"/>
</states>
<arguments>
<argument name="*"/>
</arguments>
<variables>
<variable name="*"/>
</variables>
</activityStateQuery>
</activityStateQueries>
</workflow>
</trackingProfile>
</profiles>
</tracking>
<tracking>
<profiles>
<trackingProfile name="StandardProfile">
<workflow>
<activityStateQueries>
<activityStateQuery activityName="*">
<states>
<state name="Faulted"/>
</states>
<arguments>
<argument name="*"/>
</arguments>
<variables>
<variable name="*"/>
</variables>
</activityStateQuery>
</activityStateQueries>
</workflow>
</trackingProfile>
</profiles>
</tracking>
<states>
tag contains sub-tags for each state you want to log. If it only contains <state name="Faulted"/>
, then only activities that end in a Faulted state, meaning they encountered an error, are logged.
<state name="Executing"/>
.
You can customize variables and arguments as well. Refer to the Microsoft documentation.
To enable driver tracing:
-
Open Command Prompt with administrator rights.
-
Access the installation directory using the
cd
argument, such ascd C:\Program Files\UiPath\Studio
. -
Run the
UiRobot.exe --enableLowLevel
command.
To disable driver tracing:
-
Open Command Prompt with administrator rights.
-
Access the installation directory using the
cd
argument, such ascd C:\Program Files\UiPath\Studio
. -
Run the
UiRobot.exe --disableLowLevel
command.
Check the About the Diagnostic Tool page in the Studio guide for information about how you can configure it to retrieve execution logs.