Result for 628AFDF58C3F117D1EB11C32DD7024C784296879

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.i386.gz
FileSize238
MD5BA6628EFAFD4F5E32DBA282D0B057926
SHA-1628AFDF58C3F117D1EB11C32DD7024C784296879
SHA-25668C69350CB3E0ACCCA727E55DB12F0134CFA2C8524F98CB2EB6F1852F1C533E0
SSDEEP6:XtWEc7slMzs2hQi/XOzEY0FownoCd3Fs1B:XU7slo3/H5owhC1B
TLSHT143D097E42088AC8EF0C26D7C01CEC870A500CB56FEBE6820009E82FA1EC100A7E28A10
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
FileSize1949700
MD58D82170AF03D4487B73E3ED2E732C097
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.3.1+ds-1+b2
SHA-17046364F78000C33DB682EE479BFA2946A749A7E
SHA-256221E132928E4A29C00C2DCE8EBFAD23E890534DC1DAF3937752D6B77BD02545F