observability: Sentry is a no-op stub and no @sentry package is installed
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- next.js, node.js, typescript
- Domain
- backend, observability
Research direction
Start with apps/web/src/lib/sentry.ts and inspect the workspace package.json files to understand the existing stub interface and available dependencies. Trace its call sites and the default alert handler before choosing the SDK integration points. Done means the web, worker, and bot errors are sent through Sentry and above-threshold alerts are routed to Slack or PagerDuty without changing call sites.
Written by the indexing model from the issue text.
Description
apps/web/src/lib/sentry.ts is a stub. Without SENTRY_DSN every call logs to stderr and returns:
export function captureException(error: unknown, context?: Record<string, unknown>): void {
if (!sentryConfig.dsn) {
console.error('[sentry-stub] exception captured:', error, context ?? '');
return;
}
No @sentry/* package is installed in any workspace package.json, so even setting the DSN would not send anything. The default alert handler only logs as well.
Why it matters
Production has no error reporting. When the worker drops a job or a webhook 500s, nobody finds out unless they are reading Railway logs at that moment. This compounds #182 (a wedged worker still reports healthy) — two independent blind spots on the same service.
Fix
Install @sentry/nextjs for apps/web and @sentry/node for the worker and bots, wire the real SDK behind the existing stub interface so call sites do not change, and route the alert handler to Slack or PagerDuty for anything above a threshold.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 4
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 7
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CopilotKit/outpost
-
area: docs area: security roadmap: now
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
CopilotKit/outpost#277 ·
Maintainers usually reply within 4 days
-
area: infrastructure roadmap roadmap: later
Difficulty 1/5 Under an hour Newbie friendliness 74/100
CopilotKit/outpost#179 ·
Maintainers usually reply within 4 days
-
area: ai roadmap roadmap: now
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/outpost#145 ·
Maintainers usually reply within 4 days
-
area: integrations priority: low roadmap roadmap: later
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
CopilotKit/outpost#124 · 3 comments ·
Maintainers usually reply within 4 days
-
area: integrations priority: low roadmap roadmap: later
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
CopilotKit/outpost#123 · 2 comments ·
Maintainers usually reply within 4 days
All issues in CopilotKit/outpost
Similar issues
-
dx hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudflare/agents#2498 ·
Maintainers usually reply within 1 day
-
Missing repro Platform: Android
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-mansion/react-native-reanimated#10816 · 2 comments ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
redhat-developer/rhdh-plugin-export-overlays#4129 ·
Maintainers usually reply within 1 day