Skip to main content

This article applies to CrashPlan PROe version 4.

Other available versions:

Version 6 | Version 5icon.qnmark.png

Code42 Support

Configure your Code42 environment to use syslog

This article applies to CrashPlan PROe version 4.

Other available versions:

Version 6 | Version 5icon.qnmark.png


In version 4.3 and later of the enterprise server, your enterprise servers can send log data to a syslog server. Syslog servers are commonly used to aggregate, monitor, and visualize log information from a variety of sources in your environment. For example, you can use Splunk to interact with your Code42 environment log data, as well as tools like Kibana or Graylog.

This article describes how to enable syslog logging in your Code42 environment.

Syslog properties

There are two parts to configuring syslog for your Code42 environment logs:

  • Configuring syslog communications for your enterprise servers
  • Configuring syslog for each log

Syslog communications

By default, syslog-enabled logs remain on the local enterprise server. Optionally, send logs to a remote syslog server by configuring the system properties for syslog's host and facility.

Syslog System Property Default Value Purpose localhost The hostname or IP address of your syslog server
c42.log.syslog.v1.facility LOCAL0 The facility keyword for syslog data

Using multiple syslog servers

The enterprise server supports sending log data to a single syslog server. If your environment uses multiple syslog servers, we recommend using an external syslog server, such as syslog-ng or rsyslog, to forward syslog data to additional syslog servers.

Individual log configuration

Each enterprise server stores operational information in several different logs. Each log can use either syslog or basic, local logging. Configure the type of logging behavior using system properties.

Code42 environment Log Purpose

Detailed records of all enterprise server activity and backup activity


High level events, such as:

  • Administration console configuration changes and the user that made them
  • Device authentication attempts
  • User, organization, and device creation
  • Enterprise server restarts
  • Errors

Records of Code42 API requests

Configuring syslog

Before you begin

These steps assume that you already have an operating syslog server. For assistance with setting up a syslog server, contact sales about engaging our PRO Services team.


Alternative commands
The example commands shown here apply to all your enterprise servers. For more information on configuring system properties, including alternative parameters that target individual enterprise servers, refer to Administration console Command-Line Interface.
  1. Sign in to your administration console.
  2. Double-click the Code42 logo to open the administration console command-line interface.
  3. Enter the following commands, adapted to your syslog configuration, to configure syslog communication:
    prop.set localhost save all
    prop.set c42.log.syslog.v1.facility LOCAL0 save all
  4. Enter the following commands to enable syslog for each log.
    Replace true with false to disable syslog for each log.
    • com_backup42_app.log
      prop.set c42.log.syslog.v1.root.enabled true save all
    • history.log
      prop.set c42.log.syslog.v1.history.enabled true save all
    • rest.log
      prop.set true save all 
  5. Restart all enterprise servers in your Code42 environment.
    1. Navigate to Destinations > Servers in the administration console.
    2. For each enterprise server:
      1. Select the enterprise server to view its details.
      2. Click Action menu > Restart Server to immediately restart the enterprise server.