Result for 412ED862141A66F4F19A05B47E3BFF20CF437351

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.s390x.gz
FileSize230
MD52EA6E6FAD6F99B0ED13A85759E0FC3E3
SHA-1412ED862141A66F4F19A05B47E3BFF20CF437351
SHA-25631F03F8951EA18E320BC5B6EE5459F56BC1FA4A50365DFD6C6DAC04FBABBB299
SSDEEP6:XtPICBVMGVMzd6ZmiynAmKdwtBMzcqA9KtVcPd46l:XJFs6ondITI9KtF6l
TLSHT176D0A7662036A452DCE6966DD0261A8A72D9C2010972ADCCE9790881F756508E98F8A9
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
FileSize2604476
MD51D57A55B5127574A12684516DE3909D5
PackageDescriptionPrometheus 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.
PackageMaintainerDebian Go Packaging Team <pkg-go-maintainers@lists.alioth.debian.org>
PackageNameprometheus-pushgateway
PackageSectionnet
PackageVersion0.7.0+ds-1+b20
SHA-1D4B8444D7140DB0C5804B21C59E020B230A2C16F
SHA-256420A92E62811BCBCF557698D7A670E36C949FFA60095411B5CC1BF7D0715453A