Result for 5D3F3EA3DF298575DECE61E56CBDB811265B71DE

Query result

Key Value
FileName./usr/bin/prometheus-pushgateway
FileSize9296472
MD588FFFA22476D5DC76219E55A0D355E76
SHA-15D3F3EA3DF298575DECE61E56CBDB811265B71DE
SHA-256DFCDBAC40FAD7EE9798C4639F6503321028E9F5261E58301E74E8423858FA980
SSDEEP49152:+nYrMCdA91ny6tPK8ZZgVhleYmjnXfjp4q8BkTUzaetnEMPFlMX:+YrMf91ny6tPK2ZAQ61aV7X
TLSHT1A6966D1A65053EA9C62D15F346EB0F3927A165846F334703C718C7BEEA5318BA762FC8
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
FileSize2401392
MD5F82B0AC97FEDBBF40EFD1CC4AC7F7E70
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-165B08B4A7281E0DEC5B402B8B2A41350E2AE99DD
SHA-256517FE0A3DB79C292BD2C8F5325520379FA97C75279CDA961D56557267880C8F7