Result for 4A14233688F431E30604E708488DF06778C39071

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.i386.gz
FileSize240
MD56C4AD66DB4A75899E5B075F755FFAC1B
SHA-14A14233688F431E30604E708488DF06778C39071
SHA-256C994C4E863D1C994E9BE8D75387482FE7B99F6015C36698AC778FB3CC89BA5BE
SSDEEP6:Xtpy+im3wWnZSHtofYRWlo8PwnGD5UKIrn0m8+Mw9/n:Xv3vS6fYMZ5UnrnUW/
TLSHT1C2D0973867D6CC36B59986E747010ACB42410CC40F2003E1847C740A6693A0E1D0014B
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
FileSize2720016
MD51B6515E842150282CB1288076BD89E7F
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-158DD9D13BEFD9534DB4D521311D35343407781BE
SHA-256E033FADB4CEACDE36DD01FB310FB8FE481B7B7BFF1E0E18604A71B49C7B1C536