8.8. Enabling Syslog
With the release of OpenShift Enterprise 2.1, you can now choose to send log files to Syslog instead of their default locations, which are found in varied locations across an OpenShift Enterprise instance. Placing them into a single location helps you to analyze broker, node, gear, and Management Console errors. See the following sections for more information on how to enable Syslog for OpenShift Enterprise components.
Note
Instructions for configuring a Syslog implementation to route to alternative destinations, such as a remote logging server, are outside of the scope of this guide. The implementation provided by Red Hat Enterprise Linux 6 is Rsyslog, which writes to the
/var/log/messages
file by default. See the Red Hat Enterprise Linux 6 Deployment Guide for information on viewing and managing log files if using Rsyslog.
8.8.1. Enabling Syslog for Broker Components
Set the
SYSLOG_ENABLED
variable in the /etc/openshift/broker.conf
file to true
in order to group production.log
, user_action.log
, and usage.log
into the syslog
file:
SYSLOG_ENABLED=trueThe default location for the
syslog
file is /var/log/messages
, but this is configurable. However, in the syslog
file, these share the same program name. In order to distinguish between the log files, the following applies:
- Messages usually sent to
production.log
will havesrc=app
in each log line. - Messages usually sent to
user_action.log
will havesrc=useraction
in each log line. - Messages usually sent to
usage.log
will havesrc=usage
in each log line.