https://blog.ohtly.com/tags/postgresql/ Recent content in PostgreSQL on OHTLY Blog Hugo zh-cn Fri, 29 May 2026 20:21:07 +0800 https://blog.ohtly.com/posts/postgresql-observability/ Fri, 29 May 2026 20:21:07 +0800 https://blog.ohtly.com/posts/postgresql-observability/ <h2 id="前言"> 前言 <a class="heading-link" href="#%e5%89%8d%e8%a8%80"> <i class="fa-solid fa-link" aria-hidden="true" title="链接到标题"></i> <span class="sr-only">链接到标题</span> </a> </h2> <p>PostgreSQL 是生产环境最常用的关系型数据库之一。当服务挂了、连接爆了、死锁了，需要第一时间感知。</p> <p>单纯靠 Prometheus 指标可以告诉你「连接数超了」，但说不出原因；单纯靠日志可以告诉你「too many connections」，但没有量化趋势。</p> <p>本文的方案是 <strong>指标 + 日志协同监控</strong>，形成完整可观测性闭环：</p> <ul> <li>指标告警 → 感知异常（量变）</li> <li>日志告警 → 定位根因（质变）</li> <li>统一通知 → 飞书即时推送</li> </ul> <h2 id="架构"> 架构 <a class="heading-link" href="#%e6%9e%b6%e6%9e%84"> <i class="fa-solid fa-link" aria-hidden="true" title="链接到标题"></i> <span class="sr-only">链接到标题</span> </a> </h2> <p>下面是完整的数据流：</p> <div class="mermaid"> graph TD PG[PostgreSQL 17<br/>monkey:5432] --> PE[postgres-exporter<br/>monkey:9187] PE --> PM[Prometheus<br/>robin:9090] PM --> AM[Alertmanager<br/>robin:9093] PG -->|Docker logs| AL[Alloy<br/>monkey:12346] AL --> LK[Loki<br/>robin:3100] LK -->|Loki Ruler LogQL| AM AM --> AT[alert-transformer<br/>robin:9091] AT --> OC[OpenClaw<br/>rivo:18789] OC --> FS[飞书] subgraph 指标路径 PE PM end subgraph 日志路径 AL LK end subgraph 通知路径 AM AT OC FS end </div> <p>两条路径独立采集、独立告警，最终汇总到同一个通知链路。</p>