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

8.4. Monitoring Broker Activity


Monitoring broker activity provides insight into the usage of your OpenShift Enterprise deployment and can help diagnose problems with it. Note that problems on the broker only affect actions that interact with the broker, such as creating applications. Deployed applications continue to function normally on their nodes even if the broker is unavailable, which means that developers can still access and update their applications using SSH and Git, and applications are still available online.

8.4.1. Default Broker Log File Locations

By default, the actions of a broker host are written locally to certain log files. The following table provides the location and a description of important broker host log files:
Expand
Table 8.1. Default Broker Log Files
File Description
/var/log/openshift/broker/production.log This file contains any log requests processed by the broker application.
/var/log/openshift/broker/user_action.log This file logs any user actions, including the creation and deletion of gears. Similar to production.log, but less verbose.
/var/log/openshift/broker/httpd/access_log This file logs any calls made to the REST API.
/var/log/openshift/broker/httpd/error_log This file logs any Rails errors that occur on start-up.
/var/log/openshift/broker/usage.log This file logs information on gear or filesystem resource usage, but only if tracking is enabled in the /etc/openshift/broker.conf file.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

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

让开源更具包容性

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

關於紅帽

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

Theme

© 2025 Red Hat