- Erste Schritte
- Grundlegendes zu UiPath Robot
- UiPath Assistant
- Installationsanforderungen
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Deploying unattended automations
- Connecting robots for unattended automations to Orchestrator
- Einrichtung von Windows Server für High-Density-Roboter
- Weiterleitung von Robotern über einen Proxy-Server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Einrichten von Linux-Robotern
- Konfigurieren der Paketsignaturüberprüfung
- Einrichten von Paketordnern und Netzwerkpfaden
- Konfigurieren von Aktivitätsfeeds
- Setting up non-persistent VDIs - follow up with Sai
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrationen
- Fehlersuche und ‑behebung
Robot-Administratorhandbuch
Log fields
A log entry contains several log fields, each holding a different information about the vent being logged.
-
Nachricht (Message) – Die Protokollmeldung
-
Level - Defines the log level.
-
Timestamp - The exact date and time the logged action was happened.
-
FileName - Der Name der Datei
.xaml
, die ausgeführt wird. -
jobId (*) - The ID of the job running the process.
-
processName (*) - The name of the process that triggered the logging. Requires an active connection to Orchestrator.
-
processVersion (*) - The version number of the process. Requires an active connection to Orchestrator.
-
windowsIdentity – Der Name des eingeloggten Benutzers, der die Aktion durchgeführt hat.
-
robotName (*) - The name of the Robot (as defined in Orchestrator).
-
machineName – Der Name der Robotermaschine.
-
machineId (*) - The id of the robot machine.
-
organizationUnitId * - Die ID der Orchestrator-Organisation.
To define custom fields, use the Add Log Fields activity. These fields appear in all subsequent logs. To remove these fields from further logs, use the Remove Log Fields activity.
Make sure to name your custom log fields different from the default log fields. Otherwise, duplicate names can corrupt the logging process and disrupt the execution of your workflow.
Diese Protokolle sind abhängig vom Protokolltyp vorhanden:
For the Execution End default log, the following fields are included:
- totalExecutionTimeInSeconds
- totalExecutionTime
For the Transaction Start default log, the following fields are included:
- Warteschlangenname (QueueName)
- transactionID
- transactionState
- initiatedBy
For the Transaction End default log, the following fields are included:
- Warteschlangenname (QueueName)
- transactionID
- transactionState
- transactionStatus
- Transaktionsausführungszeit
- Der Typ Verarbeitungsausnahme
- Grund für Verarbeitungsausnahme
- queueItemReviewStatus
- queueItemPriority
For the Debugging Log default log, the following fields are included:
-
activityInfo, which is a JSON message with the following fields:
- DisplayName
- Status (State) (Faulted, Closed, Executing)
- Aktivität
-
Argumente