订阅

UiPath Orchestrator

UiPath Orchestrator 指南

关于日志

The Logs page displays logs generated by Robots in all folders the user has access to, including logs generated for jobs started through remote debugging sessions.
如需访问,请从文件夹上下文导航到 Orchestrator“自动化”选项卡,然后从显示的选项中选择“日志”

单击以获取“日志”页面的字段说明

Field

Description

Time

The timestamp the log was registered.

You can sort and filter the log list by Time.

Level

The severity level at which the message was logged. The following options are available: Trace, Debug, Info, Warn, Error, and Fatal.

You can sort and filter the log list by Level.

Process

The name of the process that generated a given log message.

Hostname

The name of the workstation used for the process execution.

Host identity

The identity under which the execution takes place. The following values are possible:
<Domain\Username> - jobs executed under that specific account. Displayed in the following cases:
foreground jobs regardless of the Robot version;
all jobs executed on Robots lower than 2021.10;
attended jobs executed on robots connected using a machine key, without user sign-in.

Note: For Robots older than 2021.10, the host identity gets populated dynamically according to the account settings made in Orchestrator. Changing the domain\username for the account used to execute a job changes the host identity as well.

ROOT - background jobs executed on Linux robots.

NT AUTHORITY\LOCAL SERVICE - jobs executed under the Robot service identity. Displayed for background jobs executed on Robots 2021.10+ without credentials.
ⓘ Service mode robots run under NT AUTHORITY\LOCAL SERVICE. User mode robots run under a certain user identity.

N/A - jobs started from the Assistant by users connected using interactive sign-in. For robots connected using the machine key, without user sign-in, the <Domain\Username> is displayed.

Message

The logged message. This can also be a message logged through the Log Message activity in Studio.
Keep in mind that the content of this column is displayed in the language of the Robot regardless of what language was chosen for Orchestrator.


📘

备注:

只能在 Orchestrator 数据库和 Elasticsearch 中查看在文件夹上下文外部生成的日志。

筛选

要查看机器人为指定作业生成的所有日志,请导航至“作业”页面。
要按生成日志的主机名筛选日志,请使用“日志”页面上的“计算机”筛选。

新筛选器可适用于 ElasticSearch 中存储的日志,而对于数据库中存储的日志,则仅适用于新的日志条目。

日志存储


If Orchestrator is unavailable, logs are stored in a local database (C:\Windows\SysWOW64\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.

📘

注意

将日志成功发送至 Orchestrator 后,系统不会删除此数据库。

作业状态存储在 UiPath 机器人服务的内存中。如果 Orchestrator 处于可用状态,则系统会在二者之间同步作业状态的相关信息。不过,如果 Orchestrator 处于不可用状态,则您在重启 UiPath 机器人服务后便会丢失此类信息。这意味着,每当 Orchestrator 处于可用状态时,您均需再次执行作业。

Logs can be sent to ElasticSearch, a local SQL database, and/or Insights thus enabling you to have non-repudiation logs. They are independent of each other and, as such, an issue encountered in one does not affect the other(s).

Configure the location where logs are stored in UiPath.Orchestrator.dll.config, by changing the value of the writeTo parameter.

如果日志发送到 Elasticsearch 或 SQL 数据库,则“日志”页面会显示机器人发送到 Orchestrator 的条目。如果日志同时发送到 Elasticsearch 和 SQL,则“日志”页面仅显示发送到 Elasticsearch 的条目。

📘

重要

如果您每周在 SQL 数据库中累积超过 200 万个机器人日志,则几个月后如果不清理较旧的日志,性能可能会下降。对于如此大量的日志,我们建议使用 Elasticsearch。请参阅此处有关日志的数据库维护程序。

If you use Elasticsearch to store your Robot logs, please note that, in certain circumstances, only 10 000 items can be queried.

由于 Elasticsearch 的限制,我们将 Cloud Platform 的 Orchestrator 租户配置为忽略大于 50 KB 的机器人日志。绝大多数日志的平均大小约为 2 KB。

日志记录级别


记录的消息包括以下级别:“Trace”、“Debug”、“Info”、“Warn”、“Error”和“Fatal”

自定义消息也可以通过“日志消息”活动从 Studio 发送到此页面。可以记录上述所有级别的消息,并且应将其用于诊断目的。

例如,在下面的屏幕截图中,您可以看到我们记录了一条严重级别为 Fatal 的自定义消息。

14551455

See Logging Levels for more information.

导出日志


通过单击“导出”按钮,可将所有日志导出到 .csv 文件。生成此文件时,系统会考虑应用到此页面的筛选器。例如,如果您设置为仅查看过去 30 天严重性级别为 Info 的日志,则仅下载符合这些条件的条目。

请注意,为了确保最佳性能,导出的条目不按时间倒序排列。

11511151

仅在以下情况下,日志的顺序可能不正确:

  • There are two or more robot log entries with almost equal timestamps - they are equal up to the millisecond (time expressed as yyyy-MM-dd HH\:mm\:ss.fff is the same), but differ in the millisecond's subunits (the last four values in yyyy-MM-dd HH\:mm\:ss.fffffff are different).
  • 在 Orchestrator 中查看日志时,日志在网格中以默认顺序排序(按时间降序排序)。

但是,这不会影响数据库和导出的 .csv文件。

📘

注意

无论用户选择哪种语言,Orchestrator 的服务器异常以及“作业详细信息”窗口上的堆栈跟踪都以英语记录。

权限


您需要在文件夹上下文中具有对日志查看权限,才能访问在该文件夹中生成的日志。

7 个月前更新


关于日志


建议的编辑仅限用于 API 参考页面

您只能建议对 Markdown 正文内容进行编辑,而不能建议对 API 规范进行编辑。