When, and how, do you even begin implementing an observability tool? Right now, it’s 1 of 2 very different scenarios for software companies:
Series B:
- Has users and revenue
- Uses revenue to hire SREs & set up dashboards/monitoring
Series A/seed-stage
- Observability is the last thing on their to-do list
- No time or $$ to invest in setting up monitoring
So, where’s the in-between? What is the on-ramp to smartly monitoring your software?
This is the #1 issue that Micha Hernandez van Leuffen is chipping away at.
How? A new API debugging tool that acts like Postman supercharged with OpenTelemetry.
It focuses on the early stage of building your API, giving you Band-Aids for the 100s of paper cuts that come w/ the process & shaving time off your development.
His company, Fiberplane, also helps developers collaborate – with automated notebooks that connect to your observability stack.
On the latest episode of Code RED, we talked about the future of observability, including how these 2 tools might connect one day … combining AI, alerts and real knowledge from previous customers to create a smart notebook that shows you the journey and cause of an issue.
You can listen to our full chat at the link 🔗 in the comments.
➡️ Follow along with me to:
- Avoid your next outage
- Learn what’s next for observability
- Hear from global leaders in the industry about what they’re building