Is observability worth it?
Quantifiable benefits of observability:
- Performance improvement over time
- Reduced MTTR
- Prevented incidents
- Reduced employee churn
- Reduced tooling
Non-quantifiable benefits of observability:
- Lesser time to value
- Improved customer experiences
- Improved innovation
Observability has taken over all the conversations in the site reliability engineering landscape. But do you know exactly how much money it can save for your business? Or is it that the observability's cost outweights the savings because of benefits? Find out all this and more in our detailed cost-benefit analysis of observability: Is Observability Worth It? A Detailed Cost-benefit Analysis.
Trending on Indie Hackers
@Hardik_Shah Totally agree that observability is important. I experience pain over the operational issues, like performance degradation, cost improvement, and incident resolution. After reading the article, one thing catches my eye: reduced tooling. I am not sure whether there are existing products providing a single system/tool/dashboard over all aspects of running software (whether it is possible). I am more inclined to a hybrid mode: still having a suite of existing tools (specific tools on log, monitoring and trace) and one layer above (like jupyter book) to aggregate observability events for UI presentation. In addition, the majority of operational events follow the same debugging process. It is best for the one layer above to automate the whole process (like anomaly detection or replaying the script to find root causes when an issue arises).