Skip to content

Use custom / forked http client, to avoid infinite loop due to warn-level-logging in Sentry default http client #1

Open
@SimonWoolf

Description

@SimonWoolf

See getsentry/sentry-elixir#157 . Current solution is to use a fork of sentry-elixir, which is nonideal (not least because hex package can't refer to github deps). Using a custom http client in sentry-logger-backend would be much better.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions