菜单
Application monitoring, logging, and observability for production applications. Use when: setting up error tracking, adding logging, creating health endpoints, configuring alerting, preparing for production, or when debugging production issues.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/cardinalconseils/lovable-skills --skill monitoring命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use when the user wants to build an AI agent, voice agent, chat agent, multi-agent system, RAG pipeline, or MCP server. Also use when the user mentions 'AI agent', 'voice agent', 'chat agent', 'RAG', 'retrieval-augmented generation', 'MCP server', 'multi-agent', 'OpenRouter', 'ElevenLabs', 'Deepgram', or 'pgvector'.
Use when the user wants to define KPIs, build a metrics framework, identify leading indicators, create a risk register, or set up governance triggers. Also use when the user mentions 'KPIs', 'metrics framework', 'leading indicators', 'lagging indicators', 'risk register', 'OKRs', 'metric governance', or 'war-gaming'.
Use when the user wants to create product photography, brand imagery, or commercial photos using AI image generation. Also use when the user mentions 'product photography', 'AI photo', 'brand imagery', 'photo direction', 'gpt-image-1', 'image generation prompt', or 'Peter Belanger style'.
基于 SOC 职业分类
正在显示 SKILL.md
| name | monitoring |
| description | Application monitoring, logging, and observability for production applications. Use when: setting up error tracking, adding logging, creating health endpoints, configuring alerting, preparing for production, or when debugging production issues. |
Monitoring turns invisible failures into visible signals. The goal is knowing when something breaks before users do.
Use JSON format with consistent fields across all log entries.
Required fields: timestamp, level, message, request_id
Useful fields: user_id (not PII), service_name, duration_ms, status_code
Log levels:
error — Something failed and needs attentionwarn — Degraded state but still functioning (slow query, retry succeeded)info — Important business events (user signup, payment processed)debug — Development detail — never in productionNever log: Passwords, API keys, tokens, session secrets, PII (emails, addresses).
Configure Sentry, LogRocket, or Bugsnag. Capture stack traces, group by root cause, alert on new error types. Tag errors with release version for regression detection.
/health — Liveness check. Returns 200 if the process is running. Used by load balancers.
/ready — Readiness check. Verifies dependencies: database, cache, external APIs. Returns 503 if any dependency is down.
External ping service (UptimeRobot, Pingdom, Better Stack) hits /health every 1–5 minutes from multiple regions. Alert on 2+ consecutive failures.
Page (immediate): 5xx error rate spike, health check failure, database unreachable.
Notify (review soon): Slow response times (p95 > threshold), elevated error rate.
Avoid alert fatigue: Every alert should have a clear action. If you ignore an alert regularly, fix it or remove it.
| Metric | Target |
|---|---|
| Response time p95 | < 500ms |
| Error rate (5xx / total) | < 0.1% |
| Uptime | 99.9%+ |
| Rationalization | Reality |
|---|---|
| "We'll add monitoring when we need it" | You need it the moment a real user touches your app. |
| "Console.log is fine" | Console.log in production is noise. Structured logging is signal. |
| "Dashboards are enough" | Nobody watches dashboards at 3am. Alerts catch what dashboards miss. |