Elixir Error Monitoring

Debug Elixir apps and prevent crashes across your entire stack with Sentry. Resolve issues with an Elixir monitoring workflow that actually improves the debugging process.

Getting Started is Simple

Edit your mix.exs file to add it as a dependency and add the :sentry package to your applications:

Click to Copy
defp deps do [ # ... {:sentry, "~> 8.0"}, {:jason, "~> 1.1"}, # if you are using plug_cowboy {:plug_cowboy, "~> 2.3"} ] end

Setup the application production environment in your config/prod.exs

Click to Copy
config :sentry, dsn: "https://<key>@sentry.io/<project>", environment_name: :prod, enable_source_code_context: true, root_source_code_path: File.cwd!(), tags: %{ env: "production" }, included_environments: [:prod]

Check our documentation for the latest instructions.

See all platforms

Elixir Monitoring with Complete Stack Traces

See details like filename and line numbers so you never have to guess with Elixir errors. Filter and group Elixir exceptions intuitively to eliminate noise. Monitor errors at scale without impacting throughput in production.

More Than Just Bug Tracking

Use issue graphs to understand the frequency, scope, and impact ofElixir errors so you can prioritize what needs to be fixed. Get alerts via email, SMS, or chat when bugs make it into production without disrupting your development workflow.

Insights Delivered

Get real-time insights immediately. Setup takes just a few minutes and typically requires only two lines of code. If you need help, we’ve built a full documentation library to handle any debugging scenario.

“Sentry has become mission-critical to the way we build and ship software.”

Daniel Lopez Ridruejo
Senior Director of Cloud Services, Bitnami

See the Full Picture of Any Elixir Exception

Understand the context that contributed to errors with tags and relevant information about your software, environment, and users.

You can also submit optional custom data to provide extra context for bug tracking that is unique to your application and business.

Find answers to the key questions: Which users are experiencing this bug? What was the value of their shopping cart?

It’s why companies that don’t have a complete view of their infrastructure are being punished:

The average cost of network downtime is around $5,600 per minute — or $300,000 per hour.

1 out of 5 online shoppers will abandon their cart because the transaction process was too slow.

On average, a two-second slowdown in page load decreases revenues by 4.3 percent.


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 and on our blog.

Sentry supports every major language, framework, and library. You can browse each of them here.

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.

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.

Supporting Resources

How Slow is Slow?

A better experience for your users. An easier life for your developers.

© 2024 • Sentry is a registered Trademark
of Functional Software, Inc.