Skip to content

Releases: getsentry/sentry-elixir

12.0.3

12 Mar 12:08

Choose a tag to compare

New Features ✨

Bug Fixes 🐛

Internal Changes 🔧

Deps Dev

  • Bump svelte from 5.53.0 to 5.53.6 in /test_integrations/tracing/svelte_mini by @dependabot in #1006
  • Bump rollup from 4.53.5 to 4.59.0 in /test_integrations/tracing/svelte_mini by @dependabot in #1007

12.0.2

02 Mar 09:46

Choose a tag to compare

Bug Fixes 🐛

12.0.1

27 Feb 10:32

Choose a tag to compare

Internal Changes 🔧

12.0.0

25 Feb 15:05

Choose a tag to compare

Logs & Telemetry Processor

Support for Structured Logs is here! 🎉 To enable:

config :sentry,
  # your config...
  enable_logs: true # <- add this!

Log events are sent to Sentry using the new TelemetryProcessor backend. You can enable it for other types of events via configuration:

config :sentry,
  # your config...
  enable_logs: true,
  telemetry_processor_categories: [:log, :error, :check_in, :transaction] # <- add this

This will become the default backend eventually, please try it out and report any issues!

You can learn more about the Telemetry Processor in our official documentation.

Related Pull Requests

Other new features

  • Support for Distributed Tracing (957)
  • Support for LiveView spans captured under single trace root (#977)
  • Add should_report_error_callback option to Oban.ErrorReporter for flexible error reporting logic (#832)
  • Handle HTTP 413 responses for oversized envelopes (#982)

Bug Fixes

  • Wrong app_name used by Igniter in prod.exs (#972)

    This requires configuring a custom propagator:

    # Configure OpenTelemetry to use Sentry propagator for distributed tracing
    config :opentelemetry,
      text_map_propagators: [
        :trace_context,
        :baggage,
        Sentry.OpenTelemetry.Propagator
      ]

Various improvements

  • Switch default HTTP client from Hackney to Finch (#897)

  • :source_code_exclude_patterns support for OTP-28.0 (#965)

    For people on OTP 28.1

    All you need is to use ~r/foo/E instead of ~r/foo/ in your config files. For example:

    config :sentry,
      enable_source_code_context: true,
      root_source_code_paths: [File.cwd!()],
      source_code_exclude_patterns: [~r/_build/E, ~r/deps/E, ~r/priv/E, ~r/test/E]
    For people on OTP 28.0

    You can convert your regexps for source_code_exclude_patterns config to strings:

    config :sentry,
      enable_source_code_context: true,
      root_source_code_paths: [File.cwd!()],
      source_code_exclude_patterns: ["/_build/", "/deps/", "/priv/", "/test/"]

11.0.4

18 Sep 13:13

Choose a tag to compare

  • Fix safe JSON encoding of improper lists (#938)

11.0.3

12 Aug 12:21

Choose a tag to compare

Various improvements

  • Allow any version of opentelemetry deps and verify minimum versions internally - this makes it possible to use sentry with tracing disabled along with older versions of opentelemetry deps (#931)

11.0.2

16 Jul 11:28

Choose a tag to compare

Bug fixes

  • Deeply nested spans are handled now when building up traces in SpanProcessor (#924)

Various improvements

  • Span's attributes no longer include db.url: "ecto:" entries as they are now filtered out (#925)

11.0.1

18 Jun 09:06

Choose a tag to compare

Various improvements

  • Sentry.OpenTelemetry.Sampler now works with an empty config (#915)

11.0.0

17 Jun 14:46

Choose a tag to compare

This release comes with a beta support for Traces using OpenTelemetry - please test it out and report any issues you find.

New features

  • Beta support for Traces using OpenTelemetry (#902)

    To enable Tracing in your Phoenix application, you need to add the following to your mix.exs:

    def deps do
      [
        # ...
        {:sentry, "~> 11.0.0"},
        {:opentelemetry, "~> 1.5"},
        {:opentelemetry_api, "~> 1.4"},
        {:opentelemetry_exporter, "~> 1.0"},
        {:opentelemetry_semantic_conventions, "~> 1.27"},
        {:opentelemetry_phoenix, "~> 2.0"},
        {:opentelemetry_ecto, "~> 1.2"},
        # ...
      ]
    

    And then configure Tracing in Sentry and OpenTelemetry in your config.exs:

    config :sentry,
      # ...
      traces_sample_rate: 1.0 # any value between 0 and 1.0 enables tracing
    
    config :opentelemetry, span_processor: {Sentry.OpenTelemetry.SpanProcessor, []}
    config :opentelemetry, sampler: {Sentry.OpenTelemetry.Sampler, [drop: []]}
  • Add installer (based on Igniter) (#876)

Various improvements

  • Tweak credit card regex handling for OTP-28 (#898)

Changelog

10.10.0

26 May 11:19

Choose a tag to compare

This release adds Telemetry crash reporting, fixes compatibility with Erlang/OTP 28, and includes several bug fixes.

New features

  • Add Telemetry integration for capturing Telemetry crash events in Sentry (#887 by @whatyouhide)
  • Add :owner option for check-ins, providing more control over cron monitoring (#879 by @Miradorn)

Bug fixes

  • Fix regexes on Erlang/OTP 28 (#889 by @josevalim)
  • Fix ignored exception in the default filter by correcting Plug.Parsers.RequestTooLarge reference (#884 by @mbaleczny)
  • Fix hyperlink tag in Sentry.LoggerBackend moduledoc (#880 by @bjacquet)
  • Remain compatible with new translation format to be introduced in Elixir 1.19 (#885 by @martosaur)

Various improvements