Skip to content

Sentry needs to be reconfigured to **not** complain when not configured #747

Description

@DougReeder

When an exception is not caught (and perhaps other errors), the console is spammed with a lot of cruft, including

 [warning] Failed to send Sentry event.Cannot send Sentry event because of invalid DSN

This is confusing, wastes developer time, and obscures the real problem.

Sentry can be self-hosted, and there are free plans, so we shouldn't remove it entirely.
It wouldn't hurt to log one message on startup if Sentry was not configured, but after that it should be silent.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions