[Task] Add error monitoring without personal data
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- observability
Research direction
Start with the two console.error call sites named in the issue: dashboard/src/pages/oauth/consent/decide.ts and packages/mcp/src/server.ts, and read docs/privacy.md for the current logging stance. Choosing a monitor and designing the alert set is a maintainer decision, so agree on it in the thread first. Done means a scrubbing hook is covered by a test using a fake event, the alerts are configured, and /privacy names any third-party monitor and what it receives.
Written by the indexing model from the issue text.
Description
Finding (from the #110 security review) - severity: low
There is no error monitoring or alerting in the repository: errors only go to console.error and the container logs (30 day retention, see docs/privacy.md), and nobody is told when the app, a deploy or the nightly backup fails.
Proposal
- Pick a monitor (error tracker and/or uptime + backup heartbeat) and wire it so events carry no personal data: no request bodies, cookies, headers, query strings, IP addresses, emails, user ids or lesson notes (scrub in a
beforeSend-style hook, add a test with a fake event). - Alert on: site down, failed deploy, backup missed or failed, migration failure.
- State the monitor and what it receives on
/privacyif it is a third party. - Review
console.errorcalls (dashboard/src/pages/oauth/consent/decide.tslogs the whole Better Auth result;packages/mcp/src/server.tslogs raw tool errors) so they cannot contain personal data.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 183
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 CGSeb/lessonfolk
-
course help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
CGSeb/lessonfolk#199 ·
Maintainers usually reply within 1 day
All issues in CGSeb/lessonfolk
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
b310-digital/teammapper#1515 ·
Maintainers usually reply within 1 day
-
onenote
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
obsidianmd/obsidian-importer#689 ·
-
In a half-screen window, the title bar cuts the workspace and version names until they can't be readOpenbug launch local use macOS Windows
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[Integration]: eRPCOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ava-labs/builders-hub#4826 ·
Maintainers usually reply within 1 day
-
记忆分析的默认模型显示与实际使用不一致Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day