Over the last months we have made numerous improvements to our agents. Read on
When things break, your first questions are typically: Why is this happening now? What changed? Who knows about these changes?
At Opbeat, we’ve have experienced this often enough to make us wonder:
How can we make it faster to debug errors?
This is what we came up with.
Two years ago we set out to build Opbeat. Traditional ops was increasingly getting outsourced to the cloud and developers were finding themselves working two jobs: Developing new features and doing ops. Two jobs is hard. Especially as ops is 24/7. Even worse when considering the existing ops toolbox: Self-hosted, custom-built tools, fragmented datasets and broken ad-hoc coordination when issues occurred.
We just released an update to two of the seminal pages on Opbeat: Your organization’s overview page, and your app’s overview page. We think they will help you get a better, faster overview of what is going on in your apps.
Today, we are introducing assignments for error groups. We think this will increase the transparency within your team on who is responsible for fixing the error groups in your apps.