Skip to main content
Contact Support

This article applies to version 6.

Other available versions:

Version 5 | Version 4icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business
Code42 Support

Configure your Code42 environment to use syslog

  1. Last updated
  2. Save as PDF

This article applies to version 6.

Other available versions:

Version 5 | Version 4icon.qnmark.png

Available in:

StandardPremiumEnterprise
Small Business

Overview

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.

Your Code42 servers can send log data to a syslog server. 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 Code42 servers
  • Configuring syslog for each log

Syslog communications

By default, syslog-enabled logs remain on the local Code42 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
c42.log.syslog.v1.host localhost The hostname or IP address of your syslog server
c42.log.syslog.v1.facility LOCAL0 The facility keyword for syslog data

Multiple syslog servers

The Code42 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 Code42 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
com_backup42_app.log

Detailed records of all Code42 server activity and backup activity
history.log

High-level events, such as:

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

Records of Code42 API requests and web requests to the administration console

Configure syslog

Before you begin

These steps assume that you already have an operating syslog server. For assistance with setting up a syslog server:

Steps

Alternative commands
The example commands shown here apply to all your Code42 servers. For more information on configuring system properties, including alternative parameters that target individual Code42 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 c42.log.syslog.v1.host 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
    • request.log 
      prop.set c42.log.syslog.v1.request.enabled true save all
  5. Restart all Code42 servers in your Code42 environment.
    1. Navigate to Storage > Servers in the administration console.
    2. For each Code42 server:
      1. Select the Code42 server to view its details.
      2. Click action menu > Restart Server to immediately restart the Code42 server.