Your games crash. Now you need to know exactly why your
players are unhappy and how you can minimize downtime.
With Sentry, bugs and crashes become an easy part of the
development process, so you can get back to what you do
best — making games.
When your code breaks, Sentry is here to help you fix it by capturing every single exception and crash your players encounter and surfacing meaningful trends to help you prioritize the issues that matter. In other words, Sentry helps you focus your resources, without having to build additional pylons.
We'll also help you integrate with your favorite apps and services, visualize data across your application, and query raw data to uncover deep insights.
Did you know that Sentry is named after the Sentry unit from Starcraft II? Why use a service that named itself after anything else? For Aiur!
With error and crash capturing, context and tag setting, and breadcrumb recording, exception handling just got easier.
That’s it! Check out the Sentry Native SDK documentation for more information.
With the correct configuration and custom data,
that context looks something like this:
Detailed error and crash reports as if your developers were connected with a debugger, including high-quality stack traces, source context, and full access to the native crash report.
Without configuration, reports contain detailed information on the operating system, device, timing and more. All information is searchable for quick cross-referencing.
Add log files to receive Breadcrumbs showing the events leading up to the crash. Include fine-grained information of game state in custom tags or even upload screenshots or links to replay-servers.
Are your highest-paying customers affected? Receive detailed analysis of error distributions and timelines, for instance, by GPU vendor or the geographical location.
The cost of maintaining in-house error monitoring is steep. Sentry improves the rate of functionality delivered and allows you to refocus those full-time resources.