Chapter plan
What you will complete
01Design Health, Readiness & Management AccessUse Actuator as an operational boundary, not a public debugging console.Expose only required management endpointsDistinguish liveness from dependency-aware readinessSecure and separate the management surface 40 min02Correlate Logs, Metrics & TracesInstrument one request so an alert can lead to a trace and then to structured diagnostic logs.Use stable low-cardinality metric tagsPropagate observation context across async boundariesLog trace identifiers without logging credentials or payload secrets 50 min03Build a Useful Prometheus & Grafana PipelineExport, scrape, query, and visualize service-level indicators instead of collecting decorative counters.Measure rates, errors, duration, and saturationAlert on user impact with a sustained windowKeep dashboards tied to an explicit operational question 40 min
Module outcome
Operate a service from symptoms to root cause without exposing sensitive management data.
Mental model
Health answers whether automation should route traffic; metrics reveal trends; traces connect latency; logs preserve discrete context.
Module checkpoint
Observable checkout
Instrument checkout latency, failures, readiness, and one downstream call.
- Custom health contributor
- Prometheus dashboard
- Trace-correlated structured logs
Final module assessment
Ready to prove mastery?
Complete all 50 questions after finishing the module lessons and checkpoint.