Metrics, release tracking, error logging and workflow - better together

Opbeat’s mission is to help developers operate their code together. And to do so, we have found that you need at a minimum four key components: Application performance metrics, release tracking, error logging and workflow.

With the upcoming launch of our metrics service for Django, we will have completed this mission. Let me explain why we think this is so important, and so useful for developers.

Traditional ops tools are typically single purpose tools that spit out single purpose reports and silo the data. This is OK if you just want to find out for example, how many errors you have got, but less helpful if you actually want to fix them. In isolation, the data is not particularly informative.

opbeat_less_noise.png

By contrast Opbeat combines error logging, release tracking, workflow & (very soon) metrics. We share the context of the data between services, so when an error happens, we can show you the code that is breaking, who wrote it, and for more nebulous errors, how it is affecting performance.

This produces a much simpler workflow, which in-turn leads to faster bug-fixing without the classic ‘who did what’ assignment hunt. The data is shared between everyone in the team, so there are less silos, and the team gets less notifications, less application switching and less noise.

Application performance metrics for Django is coming to Opbeat very soon.

Application performance metrics for Django are here!

About the author
Rasmus Makwarth is co-founder and CEO of Opbeat. Rasmus is passionate about making the life of developers more productive, and consumes substantial amounts of coffee.
You can follow him on Twitter or connect on LinkedIn.