Result for 283494BE7CB92D7758B166F220EDED0FA6AFE875

Query result

Key Value
FileName./usr/share/doc/prometheus-pushgateway/changelog.Debian.amd64.gz
FileSize239
MD5A5F7F827D2F4EB17290CF994B40319DE
SHA-1283494BE7CB92D7758B166F220EDED0FA6AFE875
SHA-25633880000C7DB7CB95EF65DB066DD69680504D67259D2DABC33EC7B4C4D1CE142
SSDEEP6:XtKoY9zyHg5dJBVKd11ihpjJ3Vabtqnrbl:Xc1zyHg5dPgd11qtVE0bl
TLSHT16BD097BC0AA328028A78A7FE29910A9EDA81E290C5008C580094D985F82C4088E69824
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
FileSize2061430
MD5E827C6E211CD92DD08B90488DC4276B4
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-199C5B6D6D376CBDF88348C63DAC3CC51E220420D
SHA-256DB74018248B3A5BAFD3EC5C7EE5828AA075B8ED02829D9705ABA74B1752E9F93