Not wired into this site. It appears here three ways: as a line in the deployment guide's list of things a production deploy eventually wants; as two DSNs the August 2026 SaaS-footprint cleanup found on older projects and left alone (a DSN can only submit events, so it was assessed and skipped); and as one of the drains evlog can write to.
That last one is the live question. Observability here is evlog's job, and #392 asks whether Sentry belongs beside it or whether evlog's own error handling is enough. Until that is ruled, the entry records the candidate, not a dependency.