Result for 41D3D5F3C6F14167E9A9B4DAA19997370EC4CD88

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.armhf.gz
FileSize232
MD58589D4A433E09B1F97E4A06AF32967E9
SHA-141D3D5F3C6F14167E9A9B4DAA19997370EC4CD88
SHA-25659D10F1534F42674C9462AC27F3A4C4E4401A977CA1E149A753657AE37A9B97B
SSDEEP6:XtwqKsKBLrHRLhKQ5WMydZx2spuwvQ0fJl:X/J0h+VdvTfr
TLSHT17CD0971201EC893BED78022B0900585512082B1937D3B230228F0BB3A080CE0180CAA2
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
FileSize2456276
MD544718CEA123EC94315D3CFBD605DB3FF
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-17701C8594648B22EDE80F5B68C7B52D500142FC2
SHA-256032DC935C77D1C36789D9F4F854BDD185454FFF55717A711A4506D5B40D75762