# Error Monitoring for Native Application Development

> Debug Native apps faster with alerts & root-cause analysis with Sentry's Native error monitoring. Request a demo to learn how to start resolving issues today.

**URL:** https://sentry.io/for/native/

---

Your applications run on end devices that provide little (if any) feedback when something goes wrong. Debug native applications faster with the power of alerts, context, and root-cause analysis.

**Documentation:** [https://docs.sentry.io/platforms/native/](https://docs.sentry.io/platforms/native/)

## Features

### Debug Files Support

Stop converting Breakpad symbols for debug files. Sentry deals directly with Microsoft PDBs, Apple dSYMs, and Linux DWARF files, providing full access to Inline Frames and reducing the barriers to uncover an error's root cause.

### Symbol Servers

Sentry pulls debug files from external sources on demand, like an S3 bucket or the Microsoft Symbol Server. Use the time saved by not uploading debug files ahead of time for something you enjoy -- like shipping clean code.

### Monitor Release Health (Releases)

Closely track user adoption, usage of the application, percentage of crash-free users and sessions. Sentry for Mobile provides insight into the impact of crashes and bugs as it relates to user experience and application versions.

### Monitor Release Health (Trends)

Measure the health of mobile releases over time and view trends with each new issue through the release details, graphs, and filters.

### Grouping

Sentry groups Events into Issues. We have maintained (and continuously improved) default rules, but you're also welcome to configure your own. After all, you know your Events best.

### Symbolication

Error reports contain a fully symbolicated backtrace displayed in the context of the source code where the error happened.

### API-Enriched Context

Deep context allows insights into user identification, settings, hardware configuration, and more. With the addition of log and configuration files, developer teams can triage and uncover the root cause of an error faster, with less impact.

### Understand The Impact

Are your highest-paying customers affected? Receive detailed analysis of error distributions and timelines, for instance, by GPU vendor or the geographical location.

### Reduce The Cost Of Maintenance

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.

## FAQ

**What is the difference between Sentry and traditional logging?**

Traditional logging provides you with a trail of events. Some of those events are errors, but many times they're simply informational. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes. We discuss in more detail [here](/vs/logging/) and on our [blog](https://blog.sentry.io/lets-get-ready-to-monitor/).

**What  languages does Sentry support?**

Sentry supports every major  language, framework, and library. You can browse each of them [here](/platforms/).

**How much does Sentry cost?**

You can get started for free. Pricing depends on the number of monthly events, transactions, and attachments that you send Sentry. For more details, visit our [pricing page](/pricing/).

**How does Sentry impact the performance of my app?**

Sentry doesn't impact a web site's performance.

If you look at the configuration options for when you initialize Sentry in your code, you'll see there's nothing regarding minimizing its impact on your app's performance. This is because our team of SDK engineers already developed Sentry with this in mind.

Sentry is a listener/handler for errors that asynchronously sends out the error/event to Sentry.io. This is non-blocking. The error/event only goes out if this is an error.

Global handlers have almost no impact as well, as they are native APIs provided by the browsers.

---

*Source: [sentry.io/for/native/](https://sentry.io/for/native/)*