robot
latest
false
- Démarrage
- Comprendre UiPath Robot
- Assistant UiPath
- Prérequis d’installation
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Configuration de Windows Server pour des Robots haute densité
- Rediriger les Robots vers un serveur proxy
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Configurer des Robots Linux
- Configuration de la vérification de la signature des paquets
- Configurer des dossiers de package et des chemins d’accès réseau
- Configurer des flux d’activité
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Intégrations
- Résolution des problèmes
- Résoudre les problèmes du service de robot UiPath
- Résoudre les problèmes d’exécution
- Résoudre les problèmes de mise en réseau
- Résolution des problèmes de connexion
- Licensing troubleshooting
- Package troubleshooting
- Résolution des problèmes .NET
- Dépannage de la journalisation
- Dépannage des problèmes de session
Guide de l’administrateur du Robot
Dernière mise à jour 17 déc. 2024
Log storage
When the Robot is connected to Orchestrator, only logs matching the level set in Assistant or Orchestrator appear on the Logs page. If Orchestrator is unavailable, logs are stored in a local path -
C:\Windows\System32\config\systemprofile\AppData\Local\UiPath\Logs\execution_log_data
, within the available disk space, until the connection is restored. When the connection is restored, the logs are sent in batches in the order they had been generated.
Important :
The Robot update overwrites and resets this file, removing any prior edits.
Additionally, log storage can be configured by editing the
NLog.config
file. Diagnostic logs are collected by the Internal type logger and are forwarded by using NLog targets. By default, execution logs are stored in a file in the %LocalAppData%\UiPath\Logs
folder. The messages are collected by the WorkflowLogging logger and can be forwarded by using NLog targets, as specified by the following parameters in the NLog.config
file:
<?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" />
</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" />
</targets>
</nlog>
Robot logs are stored differently, based on the user running the automation, which can be the local user (for User Mode robots), or the Local System user (for Service Mode robots):
Log type |
Storage for Service Mode robots |
Storage for User Mode robots |
---|---|---|
Execution logs in
.log format
|
|
|
Execution logs in LiteDB format |
|
|
Diagnostic (or internal) logs |
|
|
Journaux de mise à jour |
|
|