You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running vault in kubernetes as a cronjob, collecting metrics is failing because Vault Benchmark shuts down immediately after printing results we’re not able to scrape the result metrics quick enough. This is running on port 2112 at the moment.
Metrics are output from the built-in HTTP load testing tool - Vegeta
Ideally we'd want it to get Vault Benchmark running in an automated way (K8s Cronjob), once a day to load test for 15 minutes in our development environment to confirm everything is looking good, we only get alerted if the results are outside expected thresholds. To do this we would need metrics to be continuously outputting the metrics or stick around for a bit at the end of the test so we can scrape the metrics.
Thanks
The text was updated successfully, but these errors were encountered:
Running vault in kubernetes as a cronjob, collecting metrics is failing because Vault Benchmark shuts down immediately after printing results we’re not able to scrape the result metrics quick enough. This is running on port 2112 at the moment.
Metrics are output from the built-in HTTP load testing tool - Vegeta
Ideally we'd want it to get Vault Benchmark running in an automated way (K8s Cronjob), once a day to load test for 15 minutes in our development environment to confirm everything is looking good, we only get alerted if the results are outside expected thresholds. To do this we would need metrics to be continuously outputting the metrics or stick around for a bit at the end of the test so we can scrape the metrics.
Thanks
The text was updated successfully, but these errors were encountered: