Skip to content

Remove Sentry integration, keep error-monitoring entry point - #170

Merged
lbougan merged 1 commit into
mainfrom
feat/remove-sentry
Oct 29, 2026
Merged

lbougan merged 1 commit into
mainfrom
feat/remove-sentry

Conversation

@cmutel

@cmutel cmutel commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Remove sentry_sdk and the sentry_sdk.init(...) call from settings.py.
  • Rename SENTRY_DSN to ERROR_MONITORING_DSN. Settings still read it and the guarded init block stays as the entry point for a future error-monitoring service. A non-empty DSN currently logs a warning that no backend is configured.
  • Update .env.SAMPLE, test env fixtures, and CHANGES.md.

Deploy notes

  • SENTRY_DSN in the production .env is no longer read and can be deleted.
  • sentry_sdk can be removed from the app venv on the next uv sync.

Test plan

  • uv run --extra testing python -m pytest: 75 passed.

Co-Authored-By: Claude noreply@anthropic.com

Drop sentry_sdk and its init call. SENTRY_DSN becomes ERROR_MONITORING_DSN,
which settings.py reads and reports on but does not wire to any service, so
the guarded init block remains as the place to plug in a future backend.

Co-Authored-By: Claude <noreply@anthropic.com>

@lbougan lbougan left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. All SENTRY_DSN references are replaced (settings, conftest, test fixture, .env.SAMPLE), the dependency is gone from pyproject, and the suite passes locally (75 passed). On the server the unit files still carry SENTRY_DSN inline; it is simply unread now, and sentry_sdk can stay in the venv until the next sync. Merging and releasing as 1.5.1.

@lbougan
lbougan merged commit 932d278 into main Oct 29, 2026
8 checks passed
@cmutel

cmutel commented Oct 30, 2026

Copy link
Copy Markdown
Contributor Author

@lbougan Thanks. Can you please confirm that this is deployed?

@cmutel
cmutel deleted the feat/remove-sentry branch October 30, 2026 07:43
@lbougan

lbougan commented Oct 31, 2026

Copy link
Copy Markdown
Member

Yep its done @cmutel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants