Monitoring a JHipster microservice architecture in practice
summary
Concrete, runnable monitoring for a JHipster microservice stack: a JHipster Console that wires logs, metrics and traces into ELK + Zipkin with Spring Cloud Sleuth for tracing, Logstash/Logback for logs, and Elasticsearch as storage. Demo uses a gateway plus two services (CRM on Postgres, accountancy on Mongo/Maria) booted via Docker Compose and Kubernetes manifests, synthetic Gatling load exercises show request traces (one took ~10s) and dashboards work; code is open source and metrics move from Dropwizard → Micrometer.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:43Monitoring microservices
- 7:14Demo
- 8:47Application overview
- 11:35Frontend tests
- 11:45Logs
- 12:35Filtering
- 13:35Metrics
- 17:05Graphs
- 19:05Request dashboard
- 20:05Tracing data
- 21:00Zipkin UI
- 22:55Request errors
- 24:05Summary
related talks
02h 42mEasy microservices with JHipster
38mObservability 101 with Spring and Micrometer
48mReactive Microservices with Spring Boot and JHipster
52mIs your JVM app flying blind? Unmask hidden issues with Observability superpowers!
44mThe Holy Trinity of Observability: Logs, Metrics, and Traces
42mMonitoring your Spring Boot & Micronaut microservices with Micrometer
45mObservability for Modern Spring Applications
42mUnified Monitoring of Containers and Microservices [I]