If I'm not mistaken, it was Shakespeare who quoted:
"Verily, in the realm of errors, not all missteps bear equal weight, nor warrant the same swift hand. Some, mere trifles, may wait, while others, of grave import, demand urgent priority."
That's not a real quote 😅 but the quote has a point: sometimes, you just want to have an overview of the errors in your application that need to be fixed now!
That's where prioritization comes into place, a new feature we've added to Flare. For each error, you can now decide which priority it needs:
We've defined four levels of priority to select from:
- Info: not really an error, just some extra info from within your system
- Low: something to pick up later on when you've got time for it
- Medium: a bug that needs to be taken care off
- High: drop everything you're working on; this issue should be resolved immediately!
When a priority is changed, we'll keep track of it in the activity overview:
Lastly, it is possible to filter errors in a project based on their priority:
Happy debugging!
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
