exsentry v0.2.1 ExSentry.Client
A GenServer which handles the capture of message/exception information
to Sentry. Not intended for end users’ direct usage; use ExSentry
as the primary interface instead.
For each outgoing request, an ExSentry.Sender process is spawned to handle the HTTP transport, including retry and error handling.
Summary
Functions
GenServer callback to initialize this server
Functions
Specs
capture_exception(Exception.t, [tuple], [{:atom, any}], %ExSentry.Client.State{dsn: term, key: term, opts: term, project_id: term, secret: term, status: term, url: term, version: term}) :: pid
Specs
capture_message(String.t, [{:atom, any}], %ExSentry.Client.State{dsn: term, key: term, opts: term, project_id: term, secret: term, status: term, url: term, version: term}) :: pid
GenServer callback to initialize this server.
Pass args[:dsn]
or add config :exsentry, dsn: "your-dsn-here"
to
config.exs
to set Sentry DSN (required). Passing a blank string ""
as DSN will disable HTTP requests, as will Mix.env == :test
.
Pass a keyword list as args[:opts]
in order to send these options
with each request to Sentry.