Insights
Unveiling error notes and the activity feed
Ruben
Today we're introducing the error activity feed. It shows you what happened with an error during its lifetime within Flare. When it was resolved, snoozed or reoccurred.
As developers, we know that two heads are better than one, especially when it comes to resolving complex issues. Enter Flare notes your secret weapon for seamless collaboration during error resolution.
On every error in Flare you can now leave notes directly. Sharing insights and hypotheses with your team in real-time. Team members can jump in, add their thoughts, and engage in discussions effortlessly.
You'll find the new notes section by clicking "show activity" on an error.
From now on when you're executing an action on an error (resolving, unresolving, snoozing and unsnoozing) then Flare will show you a new dialog where you can now leave a note behind with the reason for executing that action.
These notes will all be shown on the activity feed which will provide more information on the why certains actions happened.
Happy error hunting!
Continue reading
One core, many clients: the new Flare JavaScript client architecture
We recently reshaped the Flare JavaScript client from a single browser library and a few thin framework specific packages into a small family of packages built on a shared, platform-agnostic core. This post explains why we did it, what the core package exposes, how the browser and Node SDKs are built on top of it, why the React, Vue, and Svelte packages sit one level higher, and how anyone can use the same core to write a Flare JS client for a platform we do not ship ourselves.
Dries
Logging is here!
Logging is now available for all Flare users! Send any log from your app to Flare and use our polished interface to filter and search your logs in real-time.
Jimi
Subscribe to Backtrace, our quarterly Flare newsletter
No spam, just news & product updates
