---
name: configuracion-prometheus
description: Guia completa para configurar Prometheus como sistema de recoleccion de metricas, almacenamiento y monitorizacion de infraestructura y aplicaciones. Cubre scraping, reglas de grabacion, alertas y descubrimiento de servicios.
license: MIT
metadata:
  id: c931ac48
  slug: configuracion-prometheus
  titulo: "Configuracion de Prometheus"
  servicio: IA-Ingenieria-MLOps
  categoria_recurso: Web-Desarrollo
  tipo: referencia
  nivel: avanzado
  idioma: es
  idioma_original: en
  acceso: gratis
  precio_eur: 0
  plataformas: [Prometheus, Linux, Docker, Kubernetes]
  dependencias: [grafana-dashboards, slo-implementation, distributed-tracing]
  licencia: { spdx: MIT, redistribuible: true, uso_comercial: true }
  fuente:
    repo: wshobson/agents
    url: https://github.com/wshobson/agents/tree/main/plugins/observability-monitoring/skills/prometheus-configuration
    commit: cc37bfd
    autor: wshobson
    nombre_original: prometheus-configuration
    duplicados_en: []
  seguridad: { veredicto: seguro, riesgo: bajo, escaneado: "2026-06-14", motor: "grep-estatico+auditor-llm" }
  ficha:
    que_hace: "Configura Prometheus para recolectar metricas de infraestructura y aplicaciones con alertas y reglas de grabacion."
    como_lo_hace: "Guia paso a paso con configuracion YAML de scrape intervals, service discovery, recording rules y endpoints de diagnostico via API REST."
  content_hash: "c931ac4836b5cf8dee71be2b6c3b3ba226f4b526b4e9f6e0a0a6358d9439df3c"
  version: 1.0.0
---

# Prometheus Configuration

Complete guide to Prometheus setup, metric collection, scrape configuration, and recording rules.

## Purpose

Configure Prometheus for comprehensive metric collection, alerting, and monitoring of infrastructure and applications.

## When to Use

- Set up Prometheus monitoring
- Configure metric scraping
- Create recording rules
- Design alert rules
- Implement service discovery

## Detailed patterns and worked examples

Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient.

## Best Practices

1. **Use consistent naming** for metrics (prefix_name_unit)
2. **Set appropriate scrape intervals** (15-60s typical)
3. **Use recording rules** for expensive queries
4. **Implement high availability** (multiple Prometheus instances)
5. **Configure retention** based on storage capacity
6. **Use relabeling** for metric cleanup
7. **Monitor Prometheus itself**
8. **Implement federation** for large deployments
9. **Use Thanos/Cortex** for long-term storage
10. **Document custom metrics**

## Troubleshooting

**Check scrape targets:**

```bash
curl http://localhost:9090/api/v1/targets
```

**Check configuration:**

```bash
curl http://localhost:9090/api/v1/status/config
```

**Test query:**

```bash
curl 'http://localhost:9090/api/v1/query?query=up'
```


## Related Skills

- `grafana-dashboards` - For visualization
- `slo-implementation` - For SLO monitoring
- `distributed-tracing` - For request tracing