# sentry-elixir **Repository Path**: mirrors_getsentry/sentry-elixir ## Basic Information - **Project Name**: sentry-elixir - **Description**: The official Elixir SDK for Sentry (sentry.io) - **Primary Language**: Unknown - **License**: MIT - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2020-09-24 - **Last Updated**: 2026-03-07 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README
_Bad software is everywhere, and we're tired of it. Sentry is on a mission to help developers write better software faster, so we can get back to enjoying technology. If you want to join us [**Check out our open positions**](https://sentry.io/careers/)_  [](https://hex.pm/packages/sentry) [](https://hexdocs.pm/sentry) This is the official Sentry SDK for [Sentry]. *💁: This README documents unreleased features (from the `master` branch). For documentation on the current release, see [the official documentation][docs].* ## Getting Started ### Install To use Sentry in your project, add it as a dependency in your `mix.exs` file. Sentry does not install a JSON library nor an HTTP client by itself. Sentry will default to the [built-in `JSON`](https://hexdocs.pm/elixir/JSON.html) for JSON and [Finch] for HTTP requests, but can be configured to use other ones. To use the default ones, do: ```elixir defp deps do [ # ... {:sentry, "~> 11.0"}, {:jason, "~> 1.4"}, {:finch, "~> 0.17.0"} ] end ``` > [!WARNING] > If you're using an Elixir version before 1.18, the Sentry SDK will default to [Jason] as the JSON library. However, you **must** add it to your dependencies: > > ```elixir > defp deps do > [ > # ... > {:sentry, "~> 10.8.1"}, > {:jason, "~> 1.4"} > ] > end > ``` ### Configuration Sentry has a range of configuration options, but most applications will have a configuration that looks like the following: ```elixir # config/config.exs config :sentry, dsn: "https://public_key@app.getsentry.com/1", environment_name: config_env(), enable_source_code_context: true, root_source_code_paths: [File.cwd!()] ``` ### Usage This library comes with a [`:logger` handler][logger-handlers] to capture error messages coming from process crashes. To enable this, add [`Sentry.LoggerHandler`](https://hexdocs.pm/sentry/Sentry.LoggerHandler.html) to your production configuration: ```elixir # config/prod.exs config :my_app, :logger, [ {:handler, :my_sentry_handler, Sentry.LoggerHandler, %{ config: %{ metadata: [:file, :line], rate_limiting: [max_events: 10, interval: _1_second = 1_000], # Logs all messages with level `:error` and above to Sentry. # Remove :capture_log_messages and :level if you only want to report crashes. capture_log_messages: true, level: :error } }} ] ``` And then add your logger when your application starts: ```elixir # lib/my_app/application.ex def start(_type, _args) do Logger.add_handlers(:my_app) # ... end ``` Alternatively, you can skip the `:logger` configuration and add the handler directly to your application's `start/2` callback: ```elixir # lib/my_app/application.ex def start(_type, _args) do :logger.add_handler(:my_sentry_handler, Sentry.LoggerHandler, %{ config: %{ metadata: [:file, :line], rate_limiting: [max_events: 10, interval: _1_second = 1_000], capture_log_messages: true, level: :error } }) # ... end ``` See all logger configuration options [here](https://hexdocs.pm/sentry/Sentry.LoggerHandler.html). #### Capture exceptions manually Sometimes you want to capture specific exceptions manually. To do so, use [`Sentry.capture_exception/2`](https://hexdocs.pm/sentry/Sentry.html#capture_exception/2). ```elixir try do ThisWillError.really() rescue my_exception -> Sentry.capture_exception(my_exception, stacktrace: __STACKTRACE__) end ``` Sometimes you want to capture **messages** that are not exceptions. To do that, use [`Sentry.capture_message/2`](https://hexdocs.pm/sentry/Sentry.html#capture_exception/2): ```elixir Sentry.capture_message("custom_event_name", extra: %{extra: information}) ``` To learn more about how to use this SDK, refer to [the documentation][docs]. #### Testing Your Configuration To ensure you've set up your configuration correctly we recommend running the included Mix task. It can be tested on different Mix environments and will tell you if it is not currently configured to send events in that environment: ```bash MIX_ENV=dev mix sentry.send_test_event ``` ### Testing with Sentry In some cases, you may want to _test_ that certain actions in your application cause a report to be sent to Sentry. Sentry itself does this by using [Bypass]. It is important to note that when modifying the environment configuration the test case should not be run asynchronously, since you are modifying **global configuration**. Not returning the environment configuration to its original state could also affect other tests depending on how the Sentry configuration interacts with them. A good way to make sure to revert the environment is to use the [`on_exit/2`][exunit-on-exit] callback that ships with ExUnit. For example: ```elixir test "add/2 does not raise but sends an event to Sentry when given bad input" do bypass = Bypass.open() Bypass.expect(bypass, fn conn -> assert {:ok, _body, conn} = Plug.Conn.read_body(conn) Plug.Conn.resp(conn, 200, ~s<{"id": "340"}>) end) Sentry.put_config(:dsn, "http://public:secret@localhost:#{bypass.port}/1") Sentry.put_config(:send_result, :sync) on_exit(fn -> Sentry.put_config(:dsn, nil) Sentry.put_config(:send_result, :none) end) MyModule.add(1, "a") end ``` When testing, you will also want to set the `:send_result` type to `:sync`, so that sending Sentry events blocks until the event is sent. ## Integrations * [Phoenix and Plug][setup-phoenix-and-plug] ## Contributing to the SDK Please make sure to read the [CONTRIBUTING.md](CONTRIBUTING.md) before making a pull request. Thanks to everyone who has contributed to this project so far.