skills.rest
yknothing
yknothingCOMMUNITY
Explore all skills by this author →
GitHub

monitoring-observability

Define telemetry signals, dashboards, and alert rules for production systems.

1|Updated Mar 17, 2026
Search Tags:#monitoring#dashboards#production#observability#alerts#telemetry
One-click install
npx skills add https://github.com/yknothing/prodcraft --skill monitoring-observability-yknothing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/yknothing/prodcraft/tree/main/skills/07-operations/monitoring-observability
Command: npx skills add https://github.com/yknothing/prodcraft --skill monitoring-observability-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring and observability translate system behavior into signals responders can trust. The goal is not to collect every metric. The goal is to make risky boundaries, user impact, and recovery state visible fast enough to guide action.

In a lifecycle-aware system, observability should preserve release intent. For brownfield work, make sure dashboards and alerts distinguish safe supported behavior from unsupported or coexistence-sensitive paths.

Core Features & Use Cases

  • Signal design: Map user-critical and boundary-critical signals from architecture, API contract, and delivery slice to determine what must succeed or fail closed.
  • Alerting & dashboards: Build actionable dashboards and alerts that guide triage and rollback decisions.
  • Use Case: When releasing a new feature, surface deploy markers and rollback health to enable safe incident responses.

Quick Start

Configure dashboards and alerts to surface user-impactful signals for production services.

Frequently Asked Questions about monitoring-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design actionable alerts for production monitoring?▼

Production observability focuses on making risky boundaries, user impact, and recovery state visible fast enough to guide action. It requires defining signals, minimal dashboards, and actionable alert rules rather than just collecting every available metric.

How do I set up dashboards and alerts for a new feature rollout?▼

Setting up dashboards and alerts for a new feature rollout involves surfacing deploy markers and rollback health. You configure monitoring-config, alert-rules, and service-dashboard outputs to distinguish safe supported behavior from coexistence-sensitive paths during releases.

When do I need release markers in my observability dashboards?▼

You need release markers in observability dashboards when preserving release intent for new deployments or brownfield work. They expose rollout health and boundaries, enabling fast triage and safe incident responses during feature releases.

Can I use this approach for monitoring existing brownfield deployments?▼

Yes, monitoring existing brownfield deployments is supported. The approach ensures dashboards and alerts distinguish safe supported behavior from unsupported or coexistence-sensitive paths within your current production systems.

Related Skills

Explore More Software Engineering Skills→
ZTE-AICloudZTE-AICloud
52

design-interface

Generate formal interface contracts from architecture documents and entity definitions.

Official
Advanced
ekremmkasapekremmkasap

incident-runbook-templates

Create structured incident runbooks with escalation paths and communication templates.

Community
Advanced
pulsemcppulsemcp

perform-release

Trigger production deployment workflows and monitor ECS rollout health.

Official
Advanced
ByronWilliamsCPAByronWilliamsCPA

observability-and-instrumentation

Instrument production code with structured logging, RED metrics, and OpenTelemetry tracing.

Official
Advanced