prombench icon indicating copy to clipboard operation
prombench copied to clipboard

Benchmark and integration testing tool for Prometheus

Results 7 prombench issues
Sort by recently updated
recently updated
newest added

I have prometheus binary in the same folder sudo ./prombench -rmtestdir -exporters inc:20 -- ./prometheus --log.level=info I am getting error "Prometheus returned exit status 1" if i do sudo strace...

If prombench had the option to output the results in a [benchcmp](https://godoc.org/golang.org/x/tools/cmd/benchcmp) compatible output, we could easily generate reports on performance changes between versions.

@ncabatoff and I had a discussion and I drafted some thoughts. It would be great to have some test groups in order to test different loads of exporters and test...

Issues #7 and #8 test ingestion and queries independently. This issue proposes a mode that tests them together. We probably don't need the adaptive behaviour of #7, we just want...

There should be a mode with a setup stage where prombench creates a dataset, and then a test stage where it runs queries, generating query performance metrics and verifying correctness...

Except for the oscillate exporter the load from generating a lot of metrics is significant: running 80 randcyclic exporters uses almost as much CPU as Prometheus does in consuming their...

The first version I wrote used an external exporter (i.e. spawned subprocess). The executable load_exporter is a vestige of that. I dropped that to simplify things, as there are many...