How to change the running intervall of "speedtest"

[onurbi]

Hi there,
3 years ago I modified the intervall speedtest will be started.
In the original version it was 30 minutes. I chaned it to 15 minutes. But I unfortunately did not note where. All

Could somebody tell me in what config (yml) file the intervall is defined? No of any found does contain "15".

To adapt the speedtest server which should be used is no problem meanwhile, simply edit the ENV var in
/root/internet-monitoring/docker-compose.yml.

In the container internet-monitoring_speedtest_1 the only process exporter.py is runnning. I forgot what mechanism will trigger it for a new test.

Regards,

Onurbi

[danifr]

Have you tried overwriting this value? https://github.com/geerlingguy/internet-pi/blob/master/example.config.yml#L21

Default seems to be 60 min.:

monitoring_speedtest_interval: 60m

[onurbi]

Yes, config.yml is the one, thank you! With ansible-playbook my_main.yml I could modify it.

But meanwhile the OS is already so old, that apt update is not working anymore. Ansible tries to update and stops working.

"monitoring_speedtest_interval" is not part of docker-compose.yml, where the Ookla server is located.

Do you have an idea, where ansible writes the content of this configs. docker compose must read this somewhere.

[danifr]

Yeah, it is actually in the prometheus scrape config https://github.com/geerlingguy/internet-pi/blob/master/templates/prometheus.yml.j2#L22

So the way it works is: every 60m (or whatever interval you have configured) prometheus access speedtest:9798/metrics, this call triggers a "speedtest runTest", when the test is finished the values are consumed by prometheus.

More info: https://docs.miguelndecarvalho.pt/projects/speedtest-exporter/#add-exporter-to-prometheus

Hope this answer your question :)

[onurbi]

Yes, thank you very much. I found it in the prometheus.yml of the docker compose environment as "scrape_interval: 15m".
Now I can change the value!

[github-actions]

This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.