monitoring
/monitoring
Design and operate application observability with metrics, logs, traces, and alerts. Use for SLO definition, dashboard design, on-call runbooks, and incident response.
- Author
- v1truv1us ↗
- Repository
- ai-eng-system ↗
- Licence
- MIT
- Last repository change
- 09.08.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 5
No signals detected. Repository changed on 09.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Design and operate application observability with metrics, logs, traces, and alerts. Use for SLO definition, dashboard design, on-call runbooks, and incident response.
Original author description
Design and operate application observability with metrics, logs, traces, and alerts. Use for SLO definition, dashboard design, on-call runbooks, and incident response.
How it works
- Current Versions (Verify Before Use)
- Core Principles
- SLO Design Template
- Metric Instrumentation
- Alert Design Rules
- Common Anti-Patterns
- Validation Checklist
- Official Resources
SKILL.md preview
--- name: monitoring description: Design and operate application observability with metrics, logs, traces, and alerts. Use for SLO definition, dashboard design, on-call runbooks, and incident response. metadata: category: user-invoked disable-model-invocation: true --- Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more. # Observability Engineering ## Current Versions (Verify Before Use) ```bash prometheus --version # Prometheus server grafana-server -v # Grafana jaeger --version # Jaeger tempo -version # Grafana Tempo ``` ## Core Principles 1. **Metrics for symptoms, logs for causes, traces for paths.** Use the right signal for the right question. 2. **Alert on symptoms, not causes.** Alert when users are affected (error rate ↑, latency ↑), not when a CPU metric crosses a threshold. 3. **SLOs define reliability.** Every service has error budget, SLO targets, and explicit consequences for budget exhaustion. 4. **Dashboards are for exploration, not alerting.** If you need a dashboard to know something is wrong, your alerts are wrong. 5. **Observability data is production code.** Instrumentation gets the same review rigor as business logic. ## SLO Design Template ``` Service: <name> SLI: <ratio of good events / total events> SLO: <target percentage> (e.g., 99.9%) Error Budget: 100% - SLO (e.g., 0.1% = 43.8 min/month) Alerting: - Fast burn: 2% budget in 1 hour → page immediately - Slow burn: 5% budget in 6 hours → page during business hours ``` **SLI types:** - Request-based: `good_requests / total_requests` (availability, latency bucket) - Window-based: `good_time_windows / total_time_windows` (uptime) ## Metric Instrumentation ### RED Method (for services) - **Rate:** Requests per second - **Errors:** Error rate (4xx, 5xx as % of total) - **Duration:** Request latency (p50, p95, p99) ### USE Method (for resources) - **Utilization:** % of resource used (CPU, memory, disk) - **Saturation:** Queue length, wait time - **Errors:** Hardware errors, failed allocations ### The Four Golden Signals 1. Latency 2. Traffic 3. Errors 4. Saturation ## Alert Design Rules - **Page only when human action is required immediately.** Everything else is a ticket or dashboard note. - **Every alert has a runbook.** If there's no runbook, there's no alert. - **Alert fatigue kills observability.** If an alert fires and nobody does anything, delete the alert. - **Use multi-window, multi-burn-rate alerts.** Single-threshold alerts are noisy. ## Common Anti-Patterns | Anti-Pattern | Why It's Wrong | Fix | |---|---|---| | "CPU > 80%" alert | CPU usage is not a user symptom | Alert on latency/error rate, investigate CPU | | Alerting on every error | Not all errors are user-facing | Alert on error rate, not count | | No SLOs | No shared definition of "broken" | Define SLIs and SLOs per service | | Dashboards as primary detection | Reactive, requires human watching | Alert on symptoms, dashboard for diagnosis | | Missing trace context | Can't correlate logs/metrics/traces | Use trace IDs in all signals | | Log everything at INFO | Expensive, noisy, hard to query | Structured logs, sampled debug, ERROR for issues | ## Validation Checklist - [ ] Every service exports RED metrics - [ ] Every service has defined SLOs with error budgets - [ ] Every page alert has a tested runbook - [ ] Alert routing goes to the right team (not a catch-all) - [ ] Dashboards answer "what happened" and "why" for known failure modes - [ ] Traces span service boundaries with propagated context - [ ] Log retention and cost are monitored ## Official Resources - [Google SRE Book — SLOs](https://sre.google/sre-book/service-level-objectives/) - [Prometheus best practices](https://prometheus.io/docs/practices/) - [Grafana alerting docs](https://grafana.com/docs/grafana/latest/alerting/) - [OpenTelemetry](https://opentelemetry.io/docs/) - [Jaeger tracing](https://www.jaegertracing.io/docs/)
Files in this package (2)
- SKILL.md 4 KB
- evals/evals.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · v1truv1us/ai-eng-system | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| motormetrics/motormetrics | 100 | MIT |
| DnsQueen/orcinus-skills | 100 | MIT |
| BasemTarekkamal/orbit | 100 | MIT |
| linanwx/nagobot | 100 | MIT |
| j4flmao/agent-skills | 95 | MIT |
| builderio/agent-native | 90 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version e7ec1c4e0795 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95observability-sre-incident-response
Use this capability for logging, metrics, traces, OpenTelemetry, error tracking, correlation IDs, dashboards, alerts, SLO burn alerts, runbooks, incident triage, root-cause analysis, postmortems, and on-call readiness. - 90observability
Instrument services with structured logs, metrics, traces (OpenTelemetry), SLO-based alerts and dashboards. Use when adding monitoring, debugging production, designing alerts, or making a service operable. - 100observability-slo
Lightweight observability and SLO practice—SLIs, SLO targets, error budgets, logs, metrics, traces, and alerting for apps and data pipelines. Use when defining monitoring, on-call alerts, or reliability targets. Triggers: "SLO", "SLI", "observability", "alerting", "error budget", "monitoring". - 100replit-observability
Set up comprehensive observability for Replit integrations with metrics, traces, and alerts. Use when implementing monitoring for Replit operations, setting up dashboards, or configuring alerting for Replit integration health. Trigger with phrases like "replit monitoring",… - 100ideogram-observability
Set up comprehensive observability for Ideogram integrations with metrics, traces, and alerts. Use when implementing monitoring for Ideogram operations, setting up dashboards, or configuring alerting for Ideogram integration health. Trigger with phrases like "ideogram… - 90observability-stack-setup
Bootstrap end-to-end observability with OpenTelemetry traces, metrics, and logs, including GenAI LLM span conventions, dashboards, alerts, and SLO/SLI definition. Use when: set up observability for the payments service, instrument with opentelemetry, add tracing and metrics,…