Skip to main content
Sentry is Lucia’s eyes when something breaks. Without this, hosted staging gets dumb fast.

Runbook phase mapping

  • Phase 1 — account access, org/project ownership, DSN references
  • Phase 7 — error tracking, traces, and deploy visibility
Primary runbook page: 08 - Live Transition Runbook

Why Sentry is in the stack

Once Lucia leaves localhost, you need to know:
  • what broke
  • where it broke
  • when it broke
  • how often it broke
  • whether deploys caused it
Otherwise you are flying blind with vibes and screenshots. Not ideal.

Lucia role

Sentry should cover:
  • Lucia Engine runtime exceptions
  • request failures
  • deployment regressions
  • traces on important paths
  • optional Admin/UI errors later

What to instrument first

Must-have first

  • POST /admin/operator-focus
  • engine startup failures
  • OpenAI call failures
  • Supabase connection failures
  • Redis connection failures later
  • auth/session-related failures that block staging use

Nice later

  • Admin/UI error capture
  • release tagging
  • distributed tracing across services

Setup checklist

Stage 1 — account and project

  • create Sentry org/project
  • choose Lucia environment naming
  • get DSN
  • define alert recipients

Stage 2 — engine instrumentation

  • add Sentry to Lucia Engine
  • capture route errors
  • capture startup errors
  • tag environment / release
  • verify real error ingestion

Stage 3 — admin coverage

  • optionally add Sentry to Admin/UI
  • verify client-side errors
  • connect deploy version tagging

Credentials + account reference

Account access

ItemValue
Account email
Org name
Dashboard URL
Project name
MFA method

Keys and references

Secret / TokenValue or 1Password ReferenceNotesRotated
DSNengine
Auth tokenCI/API use
Org slug
Project slug

Environment variable tracker

VariableValue / ReferenceUsed In
SENTRY_DSNEngine
VITE_SENTRY_DSNAdmin/UI optional
SENTRY_AUTH_TOKENCI/release tooling
SENTRY_ENVIRONMENTEngine/Admin
SENTRY_RELEASEoptional later

Alerting notes

Alert recipients

Alert thresholds

  • critical route failures:
  • deploy regression alerts:
  • auth failure spikes:
  • Redis failure alerts:

Notes / gotchas

  • If Lucia is hosted and not instrumented, you are basically debugging by candlelight.
  • Sentry is not glamorous. Good. Neither is a fire extinguisher.