Result for 199F04AA532239F5F36750CA6471D3BCE693026F

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.armhf.gz
FileSize235
MD52EEFC32B7BF79B3406D4CD75A27EDEDF
SHA-1199F04AA532239F5F36750CA6471D3BCE693026F
SHA-2561A42A2E10A38704B536A0BA7706D4BFAB2A30752A33AC2057CAE5DD7345F2E50
SSDEEP6:XtIclxlalZ+O9aJLE0K9jzg6p6Jr1+y4hT07B8BE:X+cZksOs16g6puMWN
TLSHT1B9D09720FF20F8B8EC2D2DEE58C0102102409B2C911EBC016080048008270162ED3C2C
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
FileSize2496252
MD546695A43122D70DCD5929362BC274301
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 <team+pkg-go@tracker.debian.org>
PackageNameprometheus-pushgateway
PackageSectionnet
PackageVersion1.4.0+ds-1+b5
SHA-1D6947814D4DA397912BD0E3E7B3A8ADF9A27FA4A
SHA-2566543AA254ACF80872125BCC53C9AFA9190EF65123ED200BC4E7352392436082B