It’s with great pleasure that we welcome Søren Louv-Jansen to Opbeat as a Frontend Engineer.
Today we released v4.13.0 of the Opbeat Node.js Agent. It includes an exciting new feature that I’ve been looking forward to releasing for quite a while: Source map support for our Node.js stack. Learn how to prepare your source maps to work well with Opbeat in this blog post.
I’ve recently been looking into improving the Opbeat support for Babel.
I had noticed that some of our users had issues getting good metrics from their Babel compiled applications, while others didn’t seem to have any issues — so what was the difference?
That’s why we decided to move source map discovery into Opbeat itself. This means it should be much more robust going forward.
Today we released v4.8.0 of the Opbeat Node.js Agent. It includes two new features that can help you when debugging performance issues and errors. Learn how to get the most out of them in this blog post.
We’re excited to start the new year with a new feature. Have you ever looked at the response times graph or the route change times graph for your app and found something interesting you want to dig deeper into? The new graph filter enables you to select a range, or even specific date point, in the graphs, so you can isolate the data on the page for a particular oddity.
We’re happy to announce truncated trace support for our Node.js stack just in time for the holidays 🎄
We know having the right information at the right time is vital in understanding and fixing a performance issue. Since releasing the updated designs for the Performance pages, we’ve worked on introducing additional context to transactions.
Today we’re happy to announce that we’re bringing Opbeat APM to Heroku as an add-on.