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.
After you create your Backtrace Universe, you will be on our “Trial Plan” for 30 days. This plan allows you to submit or upload up to 25,000 crashes, and gives you an opportunity to explore how Backtrace can help your organization better understand and resolve crashes your users encounter. You can add a total of 5 users at your organization to work with you on the trial.
After your trial is over, you will need to upgrade your account to the tier appropriate to your needs based on user and crash limits. You can find this by going to “Configure Organization” in your Console instance, and then going to Universe Settings and clicking “Billing”. If none of these plans match your requirements, reach out to email@example.com.
Should you decide not to continue with a tier after your 30-day trial is over, your Console access will be locked. Our team will deactivate your instance shortly after your trial ends, so please act quickly if you are interested in proceeding with Backtrace.
Contact us; we’re happy to discuss your needs.
The free and self-service tiers impose limits on how many user accounts can be created, how many crashes per month can be ingested, and how long crash dumps and metadata is retained. If you reach your monthly crash limit, Backtrace will offer you the option to upgrade to a higher tier to accept more crashes, or it will begin dropping additional crashes that are submitted for the month.
Backtrace will alert you in the console and via email when you reach 80% of your crash limit for the month. You can choose to upgrade to one of the higher tiers via the Billing Page in the console, or contact us.
Backtrace offers free and paid pricing tiers. Depending on the tier, there are some limitations on users, number of monthly errors, storage space, and retention periods.
- Free – Our free tier was created for low volume, single user environments. We also support qualified open source projects on our free tier.
- Backtrace is free for single user accounts with up to 250 crashes per month.
- Backtrace also offers an Open Source option for free to qualifying projects. Check out our Open Source page for more information.
- Paid – Our paid tiers can run on multi-tenant hosted environment or on-premises deployments. By default, instances have capacity for a large number of monthly errors, 100GB of storage space, and 90 day retention. Customers who require additional capacity or customized retention can contact us for more details.
Once logged into your Backtrace instance, an admin user (the first user who signed up, or any other user with the role “admin”) will be able to choose a plan to for your organization.
Choose “Configure Organization” and the “Billing” tab. From here, you can see your current usage, and choose different plans and payment methods.
The Enterprise tier provides flexible deployment options, priority support, and additional capabilities that may be useful to your organization. These include:
- Advanced Crash Capture tools
- Extensible Snapshot Generator for Linux Coredumps
- Native support for Apache Traffic Server
- Custom Retention Periods
- Control how long to retain dump files and metadata
- Additional Security and Compliance options
- PII Data Scrubbers
- SAML based SSO
- Customized Deployments
- Backtrace can provide dedicated hosted instances, or help you deploy on premises.
- Option for custom terms and invoicing
- The Backtrace team can work with your organization to create a plan that is right for you. Contact us to start the discussion!
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.
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.
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.
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.
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
Our standard plans include 90-day data retention for dump files, and either 90- or 365-days retention for metadata. We have custom retention plans for our enterprise plans.
Need something else? Let us know at email@example.com.
Yes. If you require enterprise solutions such as on-premise deployment, please reach out to us via Contact Us.
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.
Have Any Other Questions?
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.