Troubleshooting Spring Boot applications with Sentry
summary
A small React frontend, a Spring Boot movie service, a rating service and RabbitMQ simulate a flaky production flow with a 33% failure rate; Sentry is added via sentry-spring-boot starter and a DSN, logs are captured with sentry-logback, and user info and git commit releases are attached. Events go into an envelope and the SDK queues up to 30 events by default; custom event processors extract business codes, breadcrumbs replay prior logs, and tracing produces transactions and spans.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:03Software bug costs
- 8:50Why bugs are hard to reproduce and fix
- 13:26Introducing Sentry
- 18:04Sentry with Spring Boot
- 29:11Enhancing error context
- 31:21Logback integration
- 36:04Performance monitoring
- 39:24Limitations and performance
related talks
47mTroubleshooting Spring Boot applications with Sentry
14mSpeed up fixing app issues using Sentry
08mMonitoring Errors and Slowdowns Across JS Applications
38mSentry as a way not to be afraid
44mObservability with Spring-based distributed systems
47mSpring Boot Observability in Practice: Actuator, Micrometer & OpenTelemetry
51mSpring Boot 2.0 Web Applications
08mMonitoring Errors and Slowdowns with a JS Frontend and Node Backend