メニュー
Metrics, logging, distributed tracing, dashboards, alerting, SLO-driven observability, post-incident analysis. Use when designing monitoring, setting up dashboards, creating alert rules, or analyzing production data.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.
Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
REST/gRPC API design, versioning strategies, error codes, request/response contracts, backward compatibility, rate limiting, OpenAPI specifications. Use when designing APIs, defining contracts, planning versioning, or ensuring API consistency.
This skill should be used when the user asks to "design a system", "architecture", "ADR", "system design", "tech stack", "choose between approaches", "coupling", "service granularity", "blueprint", "component design", "API contract", "schema design", "trade-offs", or discusses "monolith", "microservices", "fitness functions", or architectural decisions.
This skill should be used when the user mentions keywords related to cicd.
| name | observability |
| description | Metrics, logging, distributed tracing, dashboards, alerting, SLO-driven observability, post-incident analysis. Use when designing monitoring, setting up dashboards, creating alert rules, or analyzing production data. |
| version | 1.0.0 |
Three pillars: Metrics (what), Logs (why), Traces (how). Use all three.
Key metrics:
Collection: Prometheus, StatsD, CloudWatch
api_latency_seconds{service="auth", endpoint="/login"} = 0.042
error_rate{service="api"} = 0.001
db_connections{pool="default"} = 42
Format: JSON for parsing
{
"timestamp": "2024-01-15T10:30:45Z",
"level": "ERROR",
"service": "user-service",
"message": "Failed to create user",
"error": "database_error",
"user_id": "user-123",
"duration_ms": 150
}
Sampling: Log 100% errors, 1% normal (reduce volume)
Trace request end-to-end:
Request: POST /api/users
├─ Auth span (5ms)
├─ Validate span (2ms)
├─ DB insert span (45ms)
│ ├─ Connection span (1ms)
│ └─ Query span (44ms)
└─ Cache update span (3ms)
Total: 55ms
Tools: Jaeger, Zipkin, Datadog
What to display:
Tools: Grafana, CloudWatch, Datadog
Good alert (actionable):
Alert: DB connection pool > 80%
Severity: CRITICAL
Action: Increase pool size or check for connection leaks
Runbook: https://wiki.example.com/alerts/db-pool-high
Bad alert (not actionable):
Alert: Disk usage > 50%
(What should I do?)
SLO: 99.9% uptime
Error budget: 8.64 hours/month
Alert: If burn rate > 1% → 30 days to fail budget
Alert: If burn rate > 10% → 3 days to fail budget
Status: Ready for observability work
Best for: Metrics, logging, alerting, SLO monitoring