Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

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=true
Copy to Clipboard Toggle word wrap
The 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 have src=app in each log line.
  • Messages usually sent to user_action.log will have src=useraction in each log line.
  • Messages usually sent to usage.log will have src=usage in each log line.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat