Skip to main content

​
Goal

In production, the fastest teams aren’t the ones who never ship bugs—they’re the ones who can detect, triage, and fix issues quickly. Launch aims to teach a high-quality baseline:
  • errors have consistent shapes/codes
  • logs don’t leak secrets/PII
  • every incident can be traced across mobile ↔ API ↔ database

​
Prerequisites

  • API logs accessible
  • Error reporting configured (optional)

​
Steps

  1. Ensure trace IDs are returned by the API
  2. Sanitize logs and error payloads
  3. Add client‑side error reporting

​
1) Correlation IDs

Every API request should have a stable identifier (requestId / traceId) that appears in:
  • API logs
  • API error responses
  • client error reports (Sentry breadcrumbs)
This is the foundation of debugging “what happened to this user” in Datadog/Sentry. Launch implementation:
  • API responses include X-Trace-Id
  • Server logs attach the same traceId
  • Error responses include { traceId } for easy copy/paste

​
2) Safe logging

Rules:
  • never log auth cookies, tokens, idTokens, refresh tokens
  • sanitize request bodies and headers before logging
  • log structured data (JSON) so Datadog can index fields

​
3) Consistent error taxonomy

Keep a small set of stable error codes and handle them explicitly:
  • UNAUTHORIZED, FORBIDDEN
  • VALIDATION_ERROR
  • RATE_LIMITED
  • UPSTREAM_TIMEOUT, UPSTREAM_ERROR
  • INTERNAL_ERROR
Client UI should branch on codes, not string matching.

​
4) Mobile UX patterns

  • a global error boundary for unexpected crashes
  • friendly error messages with retry actions for network failures
  • treat cancellations (e.g. aborting streaming) as non-errors

​
Sentry / Datadog guidance (high-level)

​
Mobile

Recommended:
  • Sentry for JS + native crash reporting
  • optional Datadog RUM for performance + network tracing
Attach:
  • app version, platform, device type
  • user ID (if your privacy policy allows)
Do not attach:
  • cookies, tokens, authorization headers

​
API

Recommended:
  • structured logs (Datadog log ingestion)
  • APM/tracing (Datadog APM or OpenTelemetry)
  • optional Sentry Node for exception + performance traces

​
Production checklist

  • rate limit auth + expensive endpoints (like streaming)
  • ensure error responses don’t leak internal stack traces
  • ensure logs are sanitized
  • confirm you can correlate a mobile error → API logs using a requestId/traceId

​
Incident debugging

Use the step‑by‑step guide in Incident Debugging.

​
Troubleshooting

  • Missing trace IDs: verify middleware and headers
  • No logs in prod: confirm log level and sink

​
Next Steps