Monitor Your Microservices with Logs, Metrics, Pings and Traces
summary
Monitors Spring Boot microservices end-to-end by shipping logs, system and app metrics, pings and distributed traces into Elasticsearch and Kibana; deploys the stack with Terraform and runs it on Elastic Cloud against 10 sample services, storing ~400 points per host and restarting a service live to show detection and recovery. Uses Filebeat, Metricbeat, Heartbeat, Packetbeat for collection, pulls Actuator/JMX metrics, parses JSON logs, and traces requests with Elastic APM so slow calls and error-heavy endpoints appear in dashboards and alerts.
AI-written summary · about
chapters (8)
- 0:00Microservices monitoring challenges
- 7:24Collecting logs with Filebeat
- 12:11Monitoring metrics with Metricbeat
- 23:47Setting up APM
- 30:37Parsing structured logs
- 37:59Analyzing error traces
- 45:28Deep service insights with LPM
- 48:28Q&A
related talks
31m360° Monitoring of Your Services
44mThe Holy Trinity of Observability: Logs, Metrics, and Traces
44mWelcome to the Metrics
44mObservability with Spring-based distributed systems
36mTools that will help you survive in the micro-service architecture
26mSpring Boot Observability
55mDemystifying Observability for Spring Applications
47mSpring Boot Observability in Practice: Actuator, Micrometer & OpenTelemetry