Have questions? We’ve got answers. If you didn’t find an answer to your question, contact us! We’re happy to chat, or we can schedule a guided walkthrough to help you better understand how Backtrace works.
- How do I get started with Backtrace?
What kind of code instrumentation is required?
Depending on the integration path, there is little to no code modification. If you’re working with native applications, you avoid code modification altogether. For other integrations, you only require a few lines of code and a couple of minutes to start capturing all of your errors.
Are there are any methods for getting backtraces from our Mac and Linux clients?
Yes! There are two commonly used libraries: breakpad and crashpad.
Breakpad is an open-source library initially developed by Google for cross-platform C/C++ crash reporting. It supports linux just fine and will work with some limitations for Mac. Find more details in our documentation here.
CrashPad, our recommended option, is an open-source library initially developed by Google as a successor to the Google Breakpad library. It was launched to address the limitations of Breakpad on Mac. You can find more details in our Crashpad documentation here.
If you’re not sure which optionis best, we’re happy to help you work through it.
Can I run Backtrace in my production environment? Or QA or development environments?
Backtrace works in all three. Backtrace does not run except when an error occurs, which means there is no performance impact during normal operations, and which makes Backtrace perfectly suited for production environments. When implemented in testing environments, Backtrace allows teams to fully investigate errors without needing to recreate the errors.
Is Backtrace self-service?
Yes! From the signup process to implementation, our goal is for our product to be self-service. Should you require access to packages or encounter any issues throughout the process, you can always Contact Us, or email us at firstname.lastname@example.org. We also invite our customers to a Slack channel to communicate with us directly.
I work in Support. How would I use Backtrace?
Support teams primarily use Backtrace to prioritize and triage errors. Backtrace differentiates groups from unique errors based on the error signature. Users can view recent errors and immediately know whether those crashes were similar to others or are new unique errors. Support users can then determine the appropriate course of action based on their SLA.
Do you have data limitations?
Not at this time. Send, store, and investigate as much error data as you have, as frequently as you’d like.
Do you have an enterprise offering?
Yes. If you require enterprise solutions such as on-premise deployment, please reach out to us via Contact Us.
What kind of support for symbols does Backtrace provide?
Backtrace offers a comprehensive solution for symbol management. As with other platforms, users can upload symbols manually through a web interface or automatically through their build systems. Even with these standard features, we have seen that users did not always have access to the symbols they need, either because they come from a third party or they may not have been uploaded.
To address these limitations, Backtrace also provides an automated symbol management feature that makes sure dependent symbols, such as those from public repos like MS Windows Libraries, or private repos for your own app, are available on demand if they don’t already exist in the system.
This means your crash reports will always be in a human readable format.
Where can I leave feedback for you?
We encourage feedback! Whether it’s about our product capabilities, language/platform support, messaging, or anything else, head over to Contact Us and drop us a line.
If you didn’t find an answer to your question, feel free to contact us and we’ll be happy to help you. You can also schedule a guided demo to help you understand Backtrace more and how it works.