Chapter 8. Monitoring

This chapter covers recommended practices for evaluating the overall health and performance of an OpenShift Enterprise deployment, as well as configuration options for gathering logs and metrics.
With the release of OpenShift Enterprise 2.1, you can now choose to collocate log files to Syslog instead of their default locations, which are found in several 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.

8.1. General System Checks

  1. Use standard system administration checks to monitor the basic health of your system. For example:
    • ensure adequate memory
    • minimize disk swapping
    • ensure adequate disk space
    • monitor file system health
  2. Monitor the services used by OpenShift Enterprise. Ensure the following are running and configured correctly:
    • MCollective
    • Mongo
    • Apache
    • ActiveMQ
    • SELinux and cgroups
  3. Use custom scripts to run checks specific to your system. Confirm that the entire system is working by checking:
    • nodes and gears are valid and consistent system-wide by running oo-admin-chk on a broker host
    • gears are created and deleted correctly
    • available statistics and capacities
    • hosts respond to MCollective using oo-mco ping