Opbeat is joining forces with Elastic – Learn more about Elastic APM

Big Spring design update

Since February, we have been working on some big updates to the look and feel of Opbeat. By considering all pages and features, and allowing ourselves to experiment, we laid the foundation for a thorough redesign. Two months’ work culminated on Wednesday, with the big release of Opbeat’s new look.

Release KPIs

Finding your way around Opbeat

First off, one of the things we’ve been hard at work on, which you actually shouldn’t notice too much, is that we’ve made it easier to find your way around Opbeat. For instance, we found it was really tedious to switch organizations, so click the drop-down with your Apps and switch right there. We’ve consolidated the Settings as well, so you won’t have to look for the right Settings for your app. We’re still working on this, making sure it’s just right.

Sleeker stream

The stream is an integral part of Opbeat, and that’s why we’ve tweaked it a few times over the past six months. We want it to provide the best experience by being easily skimmable for a quick overview, but to also pull your attention towards things you need to act on - like alarms and comments.

Communication is really important within a development team and that is why we have made comments stand out even more. Whether you’re just telling the team that you fixed an issue, or congratulating a co-worker on a big release, comments are in focus. To keep the conversation in your team flowing, just hit the reply button.


Improved detail views

For Error Groups and Releases, we have grouped the most important information together in the top for an easy overview of the data. The Activity Log creates a very clear timeline of events that allows any team member to easily understand what’s going on.

For the Error Group page, we have introduced a few neat improvements. One of them is filtered stacktraces. Before, you would see the full stacktrace of the whole error, with library code and everything. In the new version, we filter out the code that is not directly in your app - allowing you to focus on locating the root cause of the issue, without having to look through unnecessary library code. (You can always click to expand the full stacktrace, if you need to).

Lastly, we have also improved the syntax highlighting, so the stacktraces should be much easier to read now.

Release details


And everything else

Besides the changes mentioned above a lot of the other pages have gotten facelifts. That includes onboarding instructions, status pages, settings pages, release list, errors list and a few others. The ones we didn’t get to already, are coming in the next weeks.

Try out the updated Opbeat, and please do get in touch with any feedback or questions you might have.

About the author
Vanja Cosic is Opbeat’s community manager, and is the go-to guy in the office for the latest tech. If you have any suggestions, feature requests or just want to troll, you can reach him at vanja@opbeat.com.
You can follow him on Twitter or GitHub.