知识卡片
Prometheus拉取模型
Prometheus客户端暴露HTTP指标端点,服务器定时发请求采集并保存带标签的时间序列;PromQL利用标签查询。标准exposition格式使多个兼容采集器可读取同一类端点。原书“广播、不通知生产者、几乎零影响”过强:HTTP请求会由目标处理,开销取决于埋点和抓取规模;pull也不保证没有数据缺口。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Open Source Telemetry Standards: Prometheus, OpenTelemetry, and Beyond · 查看原书依据
Prometheus is inspired by Google’s Borgmon monitoring system (Borg). Instead of using a sink that pushes data to an aggregator system, Prometheus instrumentation exposes a metric endpoint (usually an HTTP endpoint in /metrics). The Prometheus server scrapes the metric endpoint. While most other systems are push-based, pushing data out toward an aggregator, Prometheus is pull-based. This represents a major innovation: because push-based systems must
参考来源
- 位置:《Cloud Native Observability》第04章《Open Source Telemetry Standards: Prometheus, OpenTelemetry, and Beyond》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Observability/_epub-src/ch04.html#prometheus)
- 结论依据:原文给出/metrics端点和服务器抓取机制;生成时官方overview/FAQ核验将广播、零影响和天然无缺口等过强表述收窄。
- 原始内容:Prometheus is inspired by Google’s Borgmon monitoring system (Borg). Instead of using a sink that pushes data to an aggregator system, Prometheus instrumentation exposes a metric endpoint (usually an HTTP endpoint in /metrics). The Prometheus server scrapes the metric endpoint. While most other systems are push-based, pushing data out toward an aggregator, Prometheus is pull-based. This represents a major innovation: because push-based systems must