Show Table of Contents
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:
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. |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.