Used to compare what each failure mode actually produces in App Insights vs Sentry, so the canary analysis providers can be judged against real telemetry rather than assumptions.

• /api/throwerror - server-side crash (unhandled throw)
• /api/throwerror2 - server-side crash (unhandled throw, v2)
• /api/servererror - server-side error (caught, handled 500)
• /api/downstreamerror - calls paulh-canary's /broken endpoint and handles the failure
• /client-error - client-side error (caught by a Sentry ErrorBoundary)
• /client-crash - client-side crash (unhandled, escapes React)

Get started by editing pages/index.tsx

Store configuration values in the .env file (use .env.local for local development). Use the prefix NEXT_PUBLIC_ for values that need to be visible on the client side. Omit the prefix for values that should only be visible on the server (e.g. API keys, secrets, etc).

Use the env('CLIENT_SIDE_VALUE') helper to use the values on the client side (no need to add the prefix) and process.env.SERVER_SIDE_VALUE on server side code.

• CLIENT_SIDE_VALUE:
• SERVER_SIDE_VALUE: