← Back to Articles
2022-08-12infra

Observability: Fixie + Umami + Sentry

  • Change: Three observability tools shipped within six days: Fixie HTTP proxy (a5f6f477 "telemetry using fixie"), Umami analytics (cedf61ad "umami tracking script added"), and Sentry browser tracing (cf214d3a "sentry config integration browser tracing").
  • Why: The upstream DCL API blocked direct browser requests (CORS), so Fixie tunneled API calls through a server-side proxy. Umami gave cookie-free, self-hosted page analytics as a GA alternative. Sentry caught chart render panics during the fast early shipping period.
  • Affected Modules: pages/api/ route handlers, _app.tsx, next.config.js, .env, .sentryclirc
  • Trade-offs:
    • Pro: Each tool was best-in-class for its concern; none overlapped.
    • Con: Three separate dashboards to check; Fixie added a paid proxy hop on every server-side upstream request, and both Fixie and GA were eventually removed.