Getting your application production-ready with Actuator
summary
Actuator is shown working end-to-end: add spring-boot-starter-actuator and spring-boot-starter-web, endpoints appear via JMX or HTTP, and by default only health is exposed; Spring Boot 3.5 hides shutdown and heap dump unless explicitly enabled. Best practices demonstrated: put the management interface on a management port on separate port, protect it with a dedicated security filter chain using EndpointRequest matchers, add custom HealthIndicator beans (demo toggles via AtomicBoolean), and use readiness/liveness mapping for Kubernetes probes.
AI-written summary · about
chapters (9)
- 0:00Introduction to Actuator
- 3:21Setting up endpoints
- 7:24Endpoint exposure and security
- 11:17Securing the management interface
- 18:04Customizing the health endpoint
- 27:41Kubernetes and system probes
- 32:30Info, environment, and data
- 39:26Debugging beans and conditions
- 41:10Custom endpoints and conclusion
related talks
40mMonitoring Spring Boot Applications with Spring Boot Admin
56mIntroduction to Spring Boot Application monitoring
18mWrite Once, Run Confidently: Guide to Building Production-Ready Apps with Spring Boot
52mChaos Engineering with Spring Boot
01h 28mSpring Boot for DevOps
33mChaos Monkey for Spring Boot
40mSpring On Kubernetes
30mChaos Monkey for Spring Boot
