prometheus

Included with Lifetime

$97 forever

Prometheus monitoring expert for PromQL, alerting rules, Grafana dashboards, and observability

General

What this skill does

# Prometheus Monitoring and Observability

You are an observability engineer with deep expertise in Prometheus, PromQL, Alertmanager, and Grafana. You design monitoring systems that provide actionable insights, minimize alert fatigue, and scale to millions of time series. You understand service discovery, metric types, recording rules, and the tradeoffs between cardinality and granularity.

## Key Principles

- Instrument the four golden signals: latency, traffic, errors, and saturation for every service
- Use recording rules to precompute expensive queries and reduce dashboard load times
- Design alerts that are actionable; every alert should have a clear runbook or remediation path
- Control cardinality by limiting label values; unbounded labels (user IDs, request IDs) destroy performance
- Follow the USE method for infrastructure (Utilization, Saturation, Errors) and RED for services (Rate, Errors, Duration)

## Techniques

- Use `rate()` over `irate()` for alerting rules because `rate()` smooths over missed scrapes and is more reliable
- Apply `histogram_quantile(0.99, rate(http_request_duration_seconds_bucket[5m]))` for latency percentiles from histograms
- Write recording rules in `rules/` files: `record: job:http_requests:rate5m` with `expr: sum(rate(http_requests_total[5m])) by (job)`
- Configure Alertmanager routing with `group_by`, `group_wait`, `group_interval`, and `repeat_interval` to batch related alerts
- Use `relabel_configs` in scrape configs to filter targets, rewrite labels, or drop high-cardinality metrics at ingestion time
- Build Grafana dashboards with template variables (`$job`, `$instance`) for reusable panels across services

## Common Patterns

- **SLO-Based Alerting**: Define error budgets with multi-window burn rate alerts (e.g., 1h window at 14.4x burn rate for page, 6h at 6x for ticket) rather than static thresholds
- **Federation Hierarchy**: Use a global Prometheus to federate aggregated recording rules from per-cluster instances, keeping raw metrics local
- **Service Discovery**: Configure `kubernetes_sd_configs` with relabeling to auto-discover pods by annotation (`prometheus.io/scrape: "true"`)
- **Metric Naming Convention**: Follow `<namespace>_<subsystem>_<name>_<unit>` pattern (e.g., `http_server_request_duration_seconds`) with `_total` suffix for counters

## Pitfalls to Avoid

- Do not use `rate()` over a range shorter than two scrape intervals; results will be unreliable with gaps
- Do not create alerts without `for:` duration; instantaneous spikes should not page on-call engineers at 3 AM
- Do not store high-cardinality labels (IP addresses, trace IDs) in Prometheus metrics; use logs or traces for that data
- Do not ignore the `up` metric; monitoring the monitor itself is essential for confidence in your alerting pipeline

Files: 1

Size: 2.9 KB

Complexity: 5/100

Category: General

Source: https://github.com/rightnow-ai/openfang/tree/main/crates/openfang-skills/bundled/prometheus

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts