Monitoring CloudBees CI on modern cloud platforms

1 minute read

CloudBees CI on modern cloud platforms runs on Kubernetes platforms and leverages existing monitoring solutions that work with Kubernetes.

To monitor operations center and managed controllers on CloudBees CI on modern cloud platforms, JMX is preferred. It is a standard way offered by the Java Virtual Machine to export relevant metrics for monitoring purpose and is supported by most monitoring solutions on the market. Our goal is to integrate with whatever monitoring solution enterprises already have deployed to monitor Kubernetes workloads.

CloudBees recommends monitoring the following resources using a monitoring tool, such as Prometheus or cAdvisor:

  • Container memory usage percentage

  • Container CPU usage percentage

  • JENKINS_HOME disk usage percentage


  • operations center and managed controller response time

  • Remaining build nodes capacity

  • Remaining master nodes capacity

  • Build/master nodes instances usage

CloudBees provides a reference implementation based on Datadog, which provides an example that can be used to inform you how to configure monitoring with your monitoring tool of choice.

In August 2020, the Jenkins project voted to replace the term master with controller. We have taken a pragmatic approach to cleaning these up, ensuring the least amount of downstream impact as possible. CloudBees is committed to ensuring a culture and environment of inclusiveness and acceptance - this includes ensuring the changes are not just cosmetic ones, but pervasive. As this change happens, please note that the term master has been replaced through the latest versions of the CloudBees documentation with controller (as in managed controller, client controller, team controller) except when still used in the UI or in code.