Why Your Rails App Has No Observability (and How to Fix It in One Hour)
Ever shipped a Rails app with no observability? You’re not alone.
In this live coaching call, I work with Petro, a developer building a real restaurant app using QR codes for digital menus. Together we uncover:
The most critical observability mistakes in new apps
How to evolve your domain model by logging the right events
Why "add logging" is a dangerous ticket
The 5-step framework for designing useful observability
How to turn spaghetti logs into powerful customer insights
Real-world examples using Rails, Semantic Logger & Honeycomb
💡 We dive deep into menu view failures, nil handling, domain inconsistencies, and the power of “event-first” thinking — all from a practical, unfiltered perspective.
🔧 Tools Used:
✅ Rails
✅ Semantic Logger
✅ OpenTelemetry
✅ RSpec
Whether you're starting from scratch or cleaning up a legacy mess, this video gives you actionable steps you can copy straight into your app.
Timestamps
00:00 Intro & context
03:45 Why “add logging” is a bad goal
10:22 The 5-step observability framework
15:33 Debugging the “empty menu” bug
21:40 Domain design meets event logging
42:00 Validating logs with JSON schema
51:10 Rails logging to Honeycomb
1:00:00 Summary & next steps