monitoring-observability

Set up Prometheus metrics, Grafana dashboards, and Winston logging for distributed applications.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill monitoring-observability-tedtv1007-ctrl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitoring-observability
Source: https://github.com/tedtv1007-ctrl/milk-skills-library/tree/main/monitoring-observability
Command: npx skills add https://github.com/tedtv1007-ctrl/milk-skills-library --skill monitoring-observability-tedtv1007-ctrl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires express, prom-client, winston.

What problem does it solve?

This skill addresses the challenge of maintaining system reliability by providing a structured approach to monitoring, logging, and alerting for applications and infrastructure.

Core Features & Use Cases

  • Metrics Collection: Instrument applications with Prometheus to track performance signals like latency, traffic, and error rates.
  • Alerting & Logging: Configure structured JSON logging and critical alert rules to identify bottlenecks and incidents before they impact users.
  • Use Case: Use this skill to set up a production-ready dashboard that tracks request rates and error percentages, while simultaneously configuring automated alerts for high memory usage or service downtime.

Quick Start

Use the monitoring-observability skill to generate a Prometheus configuration and a set of alert rules for a Node.js application.

Frequently Asked Questions about monitoring-observability

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

FAQPage Schema
How do I set up Prometheus metrics and Grafana dashboards for a Node.js application?

To set up Prometheus metrics and Grafana dashboards for a Node.js application, this skill instruments your code with prom-client to track latency, traffic, and error rates, and generates the corresponding dashboard configurations.

What is the best way to configure structured logging for incident response?

The best way to configure structured logging for incident response is using Winston to output structured JSON logs, enabling you to identify bottlenecks and incidents quickly before they impact users.

Can I use this to implement automated alerting rules for high memory usage?

Yes, you can implement automated alerting rules for high memory usage or service downtime by defining critical alert rules and health checks that trigger proactive alerts based on your defined SLOs.

Does this observability framework support distributed applications and infrastructure?

Yes, this observability framework supports distributed applications and infrastructure by facilitating comprehensive monitoring setups that ensure system reliability across distributed services through defined SLOs and health checks.

How do I define SLOs and health checks for production-ready monitoring?

You define SLOs and health checks for production-ready monitoring by implementing structured observability frameworks that track request rates and error percentages, ensuring system reliability through proactive alerting mechanisms.