Agent skill · data analytics · aj-geddes
prometheus-monitoring
Set up Prometheus monitoring for applications with custom metrics, scraping configurations, and service discovery. Use when implementing time-series metrics collection, monitoring applications, or building observability infrastructure.
Why this skill is useful
Provides specific configurations and best practices for setting up Prometheus monitoring that the AI wouldn't reliably generate on its own.
What it needs
Requires prometheus installed locally. About 1k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Prometheus Monitoring Table of Contents Overview When to Use Quick Start Reference Guides Best Practices Overview Implement comprehensive Prometheus monitoring infrastructure for collecting, storing, and querying time-series metrics from applications and infrastructure. When to Use Setting up metrics collection Creating custom application metrics Configuring scraping targets Implementing service discovery Building monitoring infrastructure Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Prometheus Configuration Prometheus Configuration Node.js Metrics Implementation Node.js Metrics Implementation Python Prometheus Integration Python Prometheus Integration Alert Rules Alert Rules Docker Compose Setup Docker Compose Setup Best Practices ✅ DO Use consistent metric naming conventions Add comprehensive labels for filtering Set appropriate scrape intervals (10-60s) Implement retention policies Monitor Prometheus itself Test alert rules before deployment Document metric meanings ❌ DON'T Add unbounded cardinality labels Scrape too frequently (< 10s) Ignore metric naming conventions Create alerts without runbooks Store raw event data in Prometheus Use counters for gauge-like values
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/prometheus-monitoring