Result for 579AFF0F41912FF5781DD7F1A06CF7A2D4A422F4

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.armel.gz
FileSize224
MD58435B1A1F0D4C00E971C289B161A247E
SHA-1579AFF0F41912FF5781DD7F1A06CF7A2D4A422F4
SHA-2561B9C109CECF5A2A72039C3CE9425487B5B4EE13F2D0235648BA8352DD8BAD3E6
SSDEEP6:Xtf2/PxKOtphdYUCfsblwG94lg/u3ZQ7dFR:XRixKOpuUblf942sAf
TLSHT1B3D023C166C5C6BCC18B59BD01643AA079F9D02AD63722017A9A61B67D4C5D054D208E
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
FileSize1788636
MD590AC2DFE72D4AA1E30D1A252BEC294C8
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-11803C2CB004B16B5A58A89EAF73381E611127808
SHA-25617169961333FBA6846C63CA8C09B0AE92428E7DACD945BB7A762EA00E8B2617E