Logging

In this sections logging is enabled or disabled for the cluster RoboServers, and how to log is defined. There are three types of logging possible, these are described below.

Database Logging

If database logging is enabled, the RoboServers will log to the RoboServer Log Database which is defined in the Design Studio settings. If 'Log Robot Input To Database' is selected, the input that robots are given will be logged to the database. NOTE: a RoboServer log database MUST be configured and enabled for database logging to work. If no database has been configured, the cluster settings will be invalid (you will be informed of this, so you can correct the problem).

Log4J

Using log4j to log you can control where the log goes using an ordinary log4j.properties file. The log4j.properties file is found in the Configuration folder in the application data folder. The default log4j.properties file logs all robot run information, robot messages and server messages into a 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. See the log4j manual for details.

When enabling this log, RoboServer will log using three different loggers.

Logger	Description
log4j.logger.kapow.servermessagelog	This logger is used for server logging that is not tied to a particular robot run.
log4j.logger.kapow.robotrunlog	To this logger information about starting and stopping robots. It includes execution time of the robot.
log4j.logger.kapow.robotmessagelog	Messages logged by robots e.g. as part of handling errors in steps. This also includes profiling if profiling is setup to output into the log.

Log4J Loggers

E-mail Logging

This will send an e-mail whenever a robot logs an error message or the server has a error message.

Property	Description
To Address	Who should receive the e-mail. You can add multiple addresses separated by ",".
From Address	The from address to be used on the e-mails.

E-mail configuration