prometheus-configuration

wshobson ｜ 雲端與基礎設施 ｜ 原文 ｜ MIT

設定 Prometheus 做指標收集、recording rule 與警報

---
name: prometheus-configuration
description: 設定 Prometheus，對基礎設施與應用程式做完整的指標收集、儲存與監控。在實作指標收集、建立監控基礎設施或設定警報系統時使用。
---

# Prometheus Configuration

Prometheus 設定、指標收集、scrape 設定與 recording rule 的完整指南。

## Purpose

設定 Prometheus，對基礎設施與應用程式做完整的指標收集、警報與監控。

## When to Use

- 建立 Prometheus 監控
- 設定指標 scraping
- 建立 recording rule
- 設計警報規則
- 實作 service discovery

## Detailed patterns and worked examples

詳細的模式文件放在 `references/details.md`。上面的導覽層不夠用時，再去讀那個檔案。

## Best Practices

1. 指標的**命名要一致**（prefix_name_unit）
2. **設定適當的 scrape 間隔**（一般 15 到 60 秒）
3. 對耗資源的查詢**使用 recording rule**
4. **實作高可用**（多個 Prometheus 實例）
5. 依儲存容量**設定保留期限**
6. **使用 relabeling** 清理指標
7. **監控 Prometheus 本身**
8. 大型部署**實作 federation**
9. 長期儲存**使用 Thanos/Cortex**
10. **記錄自訂指標**

## Troubleshooting

**檢查 scrape 目標：**

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

**檢查設定：**

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

**測試查詢：**

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


## Related Skills

- `grafana-dashboards` - 用於視覺化
- `slo-implementation` - 用於 SLO 監控
- `distributed-tracing` - 用於請求追蹤

---
name: prometheus-configuration
description: Set up Prometheus for comprehensive metric collection, storage, and monitoring of infrastructure and applications. Use when implementing metrics collection, setting up monitoring infrastructure, or configuring alerting systems.
---

# 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