You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After removing Sentry (#110, follow-up to #109) the project will have no error tracking, no performance monitoring, and no log aggregation in production. We still want those capabilities — we just don't want them from Sentry. Need to pick a replacement (or deliberately decide "nothing for now") before any new SDK lands.
Problem / motivation
After removing Sentry (#110, follow-up to #109) the project will have no error tracking, no performance monitoring, and no log aggregation in production. We still want those capabilities — we just don't want them from Sentry. Need to pick a replacement (or deliberately decide "nothing for now") before any new SDK lands.
Constraints to weigh:
Proposed solution
Produce a written comparison of viable options and a recommendation. At minimum cover:
For each: dev-mode overhead, vendor lock-in risk, cost at low traffic, integration effort, what we'd lose vs Sentry today.
Deliverable: an ADR-style doc (or just a comment on this issue) recommending an option, then file an implementation ticket.
Alternatives considered
Affected area
cross-cutting / unsure
Additional context