Debugging Schrödinger's App
summary
A small Flask to‑do app intentionally generates 4xx/5xx responses (including the 418 “I’m a teapot” joke) so deployed failures can be reproduced and inspected. The demo uses Flask + SQLAlchemy locally and as a Docker container on AWS ECS + SQS, with an auto‑instrumented Python tracer using OpenTelemetry traces and a Lumigo tracer token to surface the exact request path, logs and queue hops that led to the error.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:31How do fallen trees check for errors?
- 3:46Building and Deploying Apps for Many Year
- 8:38Schrodinger's Rules of Observability
- 12:54Debugging Schrödinger's App Routes
- 19:49Distributed Tracing
- 21:00Agentless Observability
- 21:38Open Telemetry (OTEL)
related talks
33mDude, Where’s My Error?: How OpenTelemetry Records Errors, and Why It...
43mDebug Like a Scientist!
51mI Can See Clearly Now: Observability of JVM & Spring Boot 2-3-4 apps
43mTaking testing to the next level
27mHow a Solo Hobbyist Learned to Love Testing
40mDebugging Elixir Code - The Tools, The Mindset
31mTesting for Graceful Failure with Vaurien and Marteau
50mDebugging HTTP