Logging

To enable logging options for cluster RoboServers, navigate to Settings > General > RoboServer log database and select the applicable options.

See also the following related topics:

Log to database

Use this option to enable database logging. The RoboServers log to the RoboServer log database, defined in the Management Console settings.

Log robot input to database

Use this option to log robot input to the database.

After you enable the "Log robot input to database" option, if you want to view inputs in the Log View>Robot runs>Input column of the log, enable the input view for each applicable cluster:

  • Navigate to Admin > RoboServers.

  • From the Action column for a cluster, select from context menu, then Cluster settings > Logging > Log robot input to database.

    If you only enable the "Log robot input to database" option in the Settings, the Input column in the Log view remains blank.

Log to Log4J

Use this option to control the destination of the logging, using an ordinary log4j2.properties file. The file is in the Configuration directory of the Kofax RPA Application Data Folder.

Example: C:\Users\name.lastname\AppData\Local\Kofax RPA\11.5.0\Configuration

See "Application Data Folder" in the Kofax RPA Installation Guide and "Audit Log for Management Console" in the Kofax RPA Administrator's Guide.

The default log4j2.properties file logs all robot run information, robot messages, and server messages into the file.

The logs are placed in the Logs folder in the application data folder. More advanced setups include storing in the Windows event log, rotating files, and the syslog.

When the Log to Log4J option is enabled, RoboServer logs using three different loggers.

Logger

Description

logger.servermessagelog.name = kapow.servermessagelog

logger.servermessagelog.level = {TRACE,INFO,DEBUG,ERROR...}

Use for server logging that is not tied to a particular robot run.

logger.robotrunlog.name = kapow.robotrunlog

logger.robotrunlog.level = {TRACE,INFO,DEBUG,ERROR...}

Use to log information about starting and stopping robots, including the execution time.

logger.robotmessagelog.name = kapow.robotmessagelog

logger.robotmessagelog.level = {TRACE,INFO,DEBUG,ERROR...}

Use to log robot messages, such as information related to error handling. Also includes profiling, if it is set to be output to the log.

Log robot input to Log4j

Use this option to log robot inputs using the log4j2.properties file.

Log to email

Use this option to send an email whenever a robot logs an error message or the server has an error message.

Property

Description

Email from

The from address to be used on the emails.

Email to

Who should receive the email. To add multiple addresses, separate them with commas.