17 Monitoring Spring with JMX
This chapter covers
- Working with Actuator endpoint MBeans
- Exposing Spring beans as MBeans
- Publishing notifications
For over a decade and a half, Java Management Extensions (JMX) has been the standard means of monitoring and managing Java applications. By exposing managed components known as MBeans (managed beans), an external JMX client can manage an application by invoking operations, inspecting properties, and monitoring events from MBeans.
We’ll start exploring Spring and JMX by looking at how Actuator endpoints are exposed as MBeans.
17.1 Working with Actuator MBeans
By default, all Actuator endpoints are exposed as MBeans. But, starting with Spring Boot 2.2, JMX itself is disabled by default. To enable JMX ...
Get Spring in Action, Sixth Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
