feat: ability to delay the speedtest (via env var SPEEDTEST_DELAY) #177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added the env var
SPEEDTEST_DELAY
to delay the running of the speedtest.What does this fix?
I've been trying to run multiple instances of this speediest export as I currently have multiple internet connections (VPN's, etc.).
Prometheus doesn't have a way to stagger the scapes, I did try and use a different internals, but this was difficult to scale to 3 speedtest exporters.
Adding a delay means I can run multiple exporters with a 15 second gap between each at regular interval (every 30m)