SupportConsoleDevelopersStart a trialContact

8.8.2. Enabling Syslog for Node Components

You can configure node hosts to send node platform and Apache logs to Syslog instead of writing to their default log file locations. After enabling Syslog logging, messages from the various node components are grouped and sent to the configured Syslog implementation. This method of aggregating log messages gives you the option to further configure your Syslog implementation to send logs directly to a remote logging server or monitoring solution without the messages being written locally to disk.

Note

Instructions for configuring a Syslog implementation to route to alternate 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.

Procedure 8.4. To Enable Syslog for Apache:

  1. Configure Apache to send log messages to Syslog by adding the following option in the /etc/sysconfig/httpd file: 
    OPTIONS="-DOpenShiftFrontendSyslogEnabled"

    Important

    All options must be on the same line. For example, in Section 8.5.2, “Enabling Application and Gear Context in Node Component Logs” another option for Apache log files is explained. If both options are desired, the line must use the following syntax: 
    OPTIONS="-Option1 -Option2"
  2. Restart the httpd service for the Apache changes to take effect: 
    # service httpd restart

Procedure 8.5. To Enable Syslog for the Node Platform:

  1. Configure the node platform to send log messages to Syslog by editing the /etc/openshift/node.conf file. Add the following line and any or all of the described optional settings that follow: 
    PLATFORM_LOG_CLASS=SyslogLogger
    Optional Threshold Setting:

    Add the following line to include messages with priorities up to and including the set threshold. Replace priority in the following line with one of the levels listed at http://ruby-doc.org/stdlib-1.9.3/libdoc/syslog/rdoc/Syslog.html#method-c-log: 

    PLATFORM_SYSLOG_THRESHOLD=priority

    Optional Trace Log Setting:

    Add the following line to include trace logs that were previously directed to the default /var/log/openshift/node/platform-trace.log file: 

    PLATFORM_SYSLOG_TRACE_ENABLED=1

  2. Restart the ruby193-mcollective service for the node platform changes to take effect: 
    # service ruby193-mcollective restart
  3. When Syslog support is enabled for the node platform, the local0 Syslog facility is used to log messages. By default, the /etc/rsyslog.conf file does not log platform debug messages. If you are using Rsyslog as your Syslog implementation, add the following line to the /etc/rsyslog.conf file to enable platform debug message logging. If necessary, replace /var/log/messages with your chosen logging destination: 
    local0.*;*.info;mail.none;authpriv.none;cron.none /var/log/messages
    Then restart the rsyslog service: 
    # service rsyslog restart
    With this change, all log messages using the local0 facility are sent to the configured logging destination.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.