monitoring-observability

Implement metrics, structured logging, distributed tracing, and alerting for production applications.

3|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/Fabric-Pro/fabric-oss --skill monitoring-observability-fabric-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/Fabric-Pro/fabric-oss/tree/main/.cursor/skills/monitoring-observability
Command: npx skills add https://github.com/Fabric-Pro/fabric-oss --skill monitoring-observability-fabric-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Production applications often lack visibility into failures, latency, and error rates, making incidents slow to detect and diagnose. This Skill provides guidance for building observability into applications so teams can detect issues quickly and respond before users are affected. ## Core Features & Use Cases - Three Pillars of Observability: Covers metrics (time-series data like CPU and requests/sec), logs (event records with context), and traces (request flow through the system). - Instrumentation Patterns: Includes a TypeScript/Express middleware example that records request duration histograms with method, route, and status code labels, plus Sentry integration for error tracking. - Use Case: When setting up monitoring for a new API service, use this Skill to add request-duration metrics, structured logging, health checks, and alert rules so on-call engineers get notified of error spikes and latency regressions. ## Quick Start Ask the AI to add request-duration metrics, structured logging, and Sentry error tracking to your Express application following the monitoring-observability guidance.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
How do I add request duration metrics to an Express app?▼

Add middleware that records the start time, then on response finish computes elapsed time and records it as a histogram labeled with method, route, and status code. This gives per-route latency visibility for dashboards and alerts.

What are the three pillars of observability?▼

The three pillars are metrics (time-series data like CPU and requests per second), logs (event records with context), and traces (request flow through the system). Together they provide full visibility into application behavior.

How do I track errors in a Node.js application?▼

Use Sentry's Node.js SDK to capture exceptions and error events automatically. Combine it with metrics on response status codes so you can correlate error spikes with specific routes and releases.

What tools can I use for monitoring dashboards and alerting?▼

Grafana is commonly used for metrics dashboards and alert rules, while Sentry handles error tracking and performance monitoring. Honeycomb provides observability-focused tracing and querying for distributed systems.

When should I implement distributed tracing instead of just logging?▼

Use distributed tracing when requests span multiple services and you need to see the full request flow and latency per hop. Logs alone cannot reconstruct cross-service causality, while traces connect spans across service boundaries.