You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/sentry/client.ex
+52-31Lines changed: 52 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ defmodule Sentry.Client do
56
56
Attempts to send the event to the Sentry API up to 4 times with exponential backoff.
57
57
58
58
The event is dropped if it all retries fail.
59
+
Errors will be logged unless the source is the Sentry.LoggerBackend, which can deadlock by logging within a logger.
59
60
60
61
### Options
61
62
* `:result` - Allows specifying how the result should be returned. Options include `:sync`, `:none`, and `:async`. `:sync` will make the API call synchronously, and return `{:ok, event_id}` if successful. `:none` sends the event from an unlinked child process under `Sentry.TaskSupervisor` and will return `{:ok, ""}` regardless of the result. `:async` will start an unlinked task and return a tuple of `{:ok, Task.t}` on success where the Task can be awaited upon to receive the result asynchronously. When used in an OTP behaviour like GenServer, the task will send a message that needs to be matched with `GenServer.handle_info/2`. See `Task.Supervisor.async_nolink/2` for more information. `:async` is the default.
0 commit comments