Alerting and External Logging

Corus supports sending alerts through SMTP when certain events occurs. It also can send its log messages to a Syslog daemon.


Corus can be configured to send email alerts in three situations:

  • When it restarts an unresponsive process;
  • when a new distribution is deployed;
  • when a distribution is undeployed.

For this feature to be enabled, the following must be configured (in the file - see the Configuration section for more on the contents of that file):

  • The corus.server.alert.enabled property must be set to true.
  • The corus.server.alert.recipients property must correspond to list of recipients (email addresses) separated by a semicolon.

In addition, you should make sure that the following properties are properly configured (defaults are used which may be unsuitable for your setup):

  • the host of the SMTP server to use for sending alerts - defaults to localhost.
  • corus.server.alert.smtp.port: the port of the SMTP server to use for sending alerts - defaults to 25.
  • corus.server.alert.smtp.password: the password to use when connecting tot he SMTP server - empty by default.
  • corus.server.alert.sender: a default one is constructed using the SMTP host.
The file that comes with Corus has complementary explanations regarding those properties.

Syslog Integration

It is possible to redirect the Corus server's internal task manager output to a Syslog daemon (the Syslog4j library is used to that end).

To activate integration with Syslog, the following properties must be confured in the $CORUS_HOME/config/ file (see the Configurationsection):

  • corus.server.syslog.protocol: specifies which protocol to use (either udp or tcp can be specified (defaults to udp).
  • specifies the host of the Syslog daemon.
  • corus.server.syslog.port: specifies the port of the Syslog daemon.

Here is an example configuration: