C

convex-sentinel

by @convexv
4.6(120)

该 Skill 可在自有 Convex 部署中接入 Sentinel 生产错误捕获,把服务端函数异常、前端 JS/React 崩溃、OCC 与扩容信号写入部署内的数据表,并在写入时默认脱敏。数据始终留在用户自己的部署里,不经过任何第三方,配合 triage 定时任务还能自动分类并为反复出现的错误生成修复 PR。

observabilityerror-trackingconvexmonitoringsreGitHub
安装方式
npx skills add https://github.com/convex/agent-skills --skill convex-sentinel
compare_arrows

Before / After 效果对比

2 组
使用前

生产环境报错后,开发者只能靠用户反馈和零散日志被动发现,翻遍多个日志入口才能拼出一次崩溃的上下文,平均要几十分钟才确认问题真实存在。

使用后

此技能把服务端异常与前端崩溃统一写入部署内数据表,并附带面包屑上下文,错误一发生即可在 CLI 中读到,定位时间压缩到几分钟。

SKILL.md

Capture production errors in your own deployment

Install @convex-dev/sentinel to capture production errors (server function failures, client JS/React crashes, OCC and scale signals) into a table in the user's OWN deployment, redacted at write time, then react to new ones. Data never leaves the user's deployment.

Workflow

  1. Install the component: app.use(sentinel) in convex/convex.config.ts.
  2. Wire the client SDK: a React error boundary plus window.onerror/unhandledrejection and breadcrumbs.
  3. Redaction runs at write time and is on by default (default-deny on secret key names and value patterns).
  4. Read recent errors with the Convex CLI (convex data, run-once-query); react to new ones via the monitor's prod_error event.
  5. Optionally enable the self-healing cron: triage classifies each error and, for recurring non-transient ones, hands it to ai-runner to open a fix PR.

Rules

  • Redaction is mandatory and on by default — never store raw secrets; the agent's reads reach the model provider.
  • Data stays in the user's deployment; never send it to a third party.
  • Sample and cap to control volume and cost.
  • Capturing PROD errors needs a deployed cloud app; install works anonymously.

用户评价 (0)

发表评价

效果
易用性
文档
兼容性

暂无评价

统计数据

安装量34.7K
评分4.6 / 5.0
版本
更新日期2026年10月23日
对比案例2 组

用户评分

4.6(120)
5
37%
4
43%
3
13%
2
5%
1
2%

为此 Skill 评分

0.0

兼容平台

🤖claude-code

时间线

创建2026年10月17日
最后更新2026年10月23日
🎁 Agent 知识卡片
调研问卷