Skip to content

Commit f165050

Browse files
committed
Remove reference to "before_send_event" in README
See: #649 (comment)
1 parent dcbd349 commit f165050

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Sentry.capture_exception(exception, [tags: %{locale: "en-us", }, user: %{id: 34}
130130

131131
By default, Sentry aggregates reported events according to the attributes of the event, but users may need to override this functionality via [fingerprinting](https://docs.sentry.io/learn/rollups/#customize-grouping-with-fingerprints).
132132

133-
To achieve that in Sentry Elixir, one can use the `before_send_event` configuration callback. If there are certain types of errors you would like to have grouped differently, they can be matched on in the callback, and have the fingerprint attribute changed before the event is sent. An example configuration and implementation could look like:
133+
To achieve that in Sentry Elixir, one can use the `before_send` configuration callback. If there are certain types of errors you would like to have grouped differently, they can be matched on in the callback, and have the fingerprint attribute changed before the event is sent. An example configuration and implementation could look like:
134134

135135
```elixir
136136
# lib/sentry.ex
@@ -146,7 +146,7 @@ end
146146

147147
# config.exs
148148
config :sentry,
149-
before_send_event: {MyApp.Sentry, :before_send},
149+
before_send: {MyApp.Sentry, :before_send},
150150
# ...
151151
```
152152

0 commit comments

Comments
 (0)