We’ve got the new configuration options and features you’ve been asking for! We are especially excited for the new configurations in the UI as it exposes the power and flexibility of major components that we have manually been tweaking for years. More about them below, but here’s the TL;DR:
- Private Symbol Servers: use the Backtrace UI to view public connect to your own symbol servers with white lists and black lists and diagnostic info for debugging symbolication problems
- Custom Deduplication Rules: use the Backtrace UI create your own fingerprinting rules for custom grouping and deduplication, with actions such as renaming functions or skipping frames that can be applied for triggered rules
- Two-Way Jira Sync: create Jira issues directly from Backtrace and see changes to issue status or assignee made in Jira from inside Backtrace
- Microsoft Teams Integration: pipe Backtrace events and notifications into Microsoft Teams channels with tagging and mentions to make sure the right people are notified
Private Symbol Servers
Do you run your own symbol servers? Do you wish you could just configure Backtrace to pull the right symbols from those servers as needed, instead of having to specially script or manually upload symbols periodically?
Now you can! 🙂 Customers who run their own symbol servers can configure Backtrace to pull the symbol files to make every crash report readable. You can have whitelists and blacklists to control exactly what you send to us under which conditions. This capability comes with it’s own set of events and notifications in the Backtrace UI so you can debug any symbolication bugs easily. Below, you can see the list of some of the pre-seeded symbol servers and usage information for connection to Microsoft’s public symbol server.
Custom Deduplication Rules
The way deduplication, grouping, and fingerprinting work in Backtrace is that all reports get run through a rules engine on our backend which does complete frame-by-frame parsing of call stacks from crashes–or line-by-line parsing of memory and other error reports–in order to identify every issue that’s actually the same or related even when there are minor variances in the reports.
Backtrace is the only product that 1) has a robust enough rules engine to do this as reports come in at scale and 2) now exposes this engine to you so you can create your own rulesets.
This will be most useful to anyone with bespoke platforms and stacks that generate, let’s call it “interesting”, errors. Read more in our help.backtrace.io article Customizing Deduplication Rules.
Two-Way Jira Sync
You’ve been able to create and associate crash and error reports in Backtrace with Jira tickets for a long time now, but it’s been a mostly manual process. Now, any ticket you create from Backtrace will be automatically updated when status or assignees change on either system!
You can even link a fingerprint in Backtrace with multiple Jira tickets and have it resolve in Backtrace only when all the Jira tickets are resolved. Check out the state logic diagram below for how the system syncs and supports multiple tickets per Backtrace fingerprint:
- Rule: A change to an external ticket will NEVER update any OTHER external ticket in away way.
- Status (aka “fingerprint;issues;state”): If ANY of the associated tickets are “open”, the fingerprint remains “in-progress”. If tickets are all “resolved”, the fingerprint can report a “resolved” state.
- Assignment (found nested in “fingerprint;issues;ticket”): These changes are ticket specific, i.e. no other ticket is involved in an assignment change
Microsoft Teams Integration
You asked; we built it. Turns out Microsoft Teams is very popular. All the same power we deliver with our Slack integration is now available with Teams: pipe events and notifications from Backtrace into specific channels with programmable mentions and tags for notifying the right people about errors and crashes.
Go forth and collaborate!
We’re trying to make Backtrace the best platform for cross-platform issue capture and debugging. Try it out and send us your feedback!