Source: prometheus-pushgateway Maintainer: Debian Go Packaging Team Uploaders: Martín Ferrari , Section: net Testsuite: autopkgtest-pkg-go Priority: optional Build-Depends: debhelper (>= 11), dh-golang, golang-any, golang-github-julienschmidt-httprouter-dev, golang-github-prometheus-client-golang-dev (>= 0.9.0-1~), golang-github-prometheus-client-model-dev, golang-github-prometheus-common-dev, golang-gopkg-alecthomas-kingpin.v2-dev (>= 2.2.6), golang-goprotobuf-dev (>= 0.0~git20150526), golang-protobuf-extensions-dev, Standards-Version: 4.2.1 Vcs-Browser: https://salsa.debian.org/go-team/packages/prometheus-pushgateway Vcs-Git: https://salsa.debian.org/go-team/packages/prometheus-pushgateway.git Homepage: https://github.com/prometheus/pushgateway XS-Go-Import-Path: github.com/prometheus/pushgateway Package: prometheus-pushgateway Architecture: any Depends: daemon, libjs-bootstrap, libjs-jquery, ${misc:Depends}, ${shlibs:Depends}, Built-Using: ${misc:Built-Using}, Description: Prometheus exporter for ephemereal jobs 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. . The Pushgateway is explicitly not an aggregator, but rather a metrics cache. It does not have a statsd-like semantics. The metrics pushed are exactly the same as you would present for scraping in a permanently running program. . For machine-level metrics, the textfile collector of prometheus-node-exporter is usually more appropriate. The Pushgateway is best used for service-level metrics.