
如果你使用 DeepSeek、元宝 AI、Copilot、ChatGPT 等 AI 工具,协助配置轩辕镜像、编写 docker pull 命令、修改 Docker Compose 镜像地址、配置镜像加速、排查镜像拉取失败、分析报错日志等问题,请先让 AI 阅读并遵守轩辕镜像的规则文档。
只需在 AI 对话中先发送下面这句话即可:
请先完整阅读并严格遵守以下文档中的全部规则与要求:
https://xuanyuan.cloud/agents.md
在未充分阅读并理解该文档前,不要生成任何命令、配置、修改建议、故障排查方案或技术回答。后续所有输出都必须严格以该文档中的规范为最高优先级执行。查看 agents.md 用法指南与完整示范。国内用户首推 元宝 AI、DeepSeek 的深度思考模式,不推荐豆包 AI;Cursor 等编辑器可在对话 @ 该链接,或加入 User Rules。 若 AI 无法访问外链,可 打开说明文档 复制全文粘贴。文档会随站点更新,复制内容可能过期,建议定期检查。
https://circleci.com/gh/prometheus/pushgateway/tree/master.svg?style=shield][circleci] https://quay.io/repository/prometheus/pushgateway/status][quay] https://img.shields.io/docker/pulls/prom/pushgateway.svg?maxAge=604800][hub]
The Prometheus Pushgateway exists to allow ephemeral and batch jobs to expose their metrics to Prometheus. Since these kinds of jobs may not exist long enough to be scraped, they can instead push their metrics to a Pushgateway. The Pushgateway then exposes these metrics to Prometheus.
First of all, the Pushgateway is not capable of turning Prometheus into a push-based monitoring system. For a general description of use cases for the Pushgateway, please read https://prometheus.io/docs/practices/pushing/.
The Pushgateway is explicitly not an aggregator or distributed counter but rather a metrics cache. It does not have https://github.com/etsy/statsd-like semantics. The metrics pushed are exactly the same as you would present for scraping in a permanently running program. If you need distributed counting, you could either use the actual statsd in combination with the https://github.com/prometheus/statsd_exporter, or have a look at the https://github.com/zapier/prom-aggregation-gateway. With more experience gathered, the Prometheus project might one day be able to provide a native solution, separate from or possibly even as part of the Pushgateway.
For machine-level metrics, the https://github.com/prometheus/node_exporter/blob/master/README.md#textfile-collector collector of the Node exporter is usually more appropriate. The Pushgateway is intended for service-level metrics.
The Pushgateway is not an event store. While you can use Prometheus as a data source for http://docs.grafana.org/reference/annotations/, tracking something like release events has to happen with some event-logging framework.
A while ago, we https://github.com/prometheus/pushgateway/issues/19 because almost all proposed use cases turned out to be anti-patterns we strongly discourage. You can follow a more recent discussion on the https://groups.google.com/forum/#!topic/prometheus-developers/9IyUxRvhY7w.
Download binary releases for your platform from the https://github.com/prometheus/pushgateway/releases and unpack the tarball.
If you want to compile yourself from the sources, you need a working Go
setup. Then use the provided Makefile (type make).
For the most basic setup, just start the binary. To change the address
to listen on, use the --web.listen-address flag (e.g. "0.0.0.0:9091" or ":9091").
By default, Pushgateway does not persist metrics. However, the --persistence.file flag
allows you to specify a file in which the pushed metrics will be
persisted (so that they survive restarts of the Pushgateway).
You can deploy the Pushgateway using the https://hub.docker.com/r/prom/pushgateway Docker image.
For example:
bashdocker pull prom/pushgateway docker run -d -p 9091:9091 prom/pushgateway
Please refer to the https://github.com/prometheus/pushgateway/blob/master/README.md for more documentation.
您可以使用以下命令拉取该镜像。请将 <标签> 替换为具体的标签版本。如需查看所有可用标签版本,请访问 标签列表页面。
来自真实用户的反馈,见证轩辕镜像的优质服务
以下是 prom/pushgateway 相关的常用 Docker 镜像,适用于 不同场景 等不同场景: