Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature-request: Logs, including "Result URL" #79

Open
samjewell opened this issue Jun 30, 2021 · 1 comment · May be fixed by #81
Open

Feature-request: Logs, including "Result URL" #79

samjewell opened this issue Jun 30, 2021 · 1 comment · May be fixed by #81
Labels
enhancement New feature or request

Comments

@samjewell
Copy link

Hello! In order to challenge my ISP and show them that they are outside the terms of my contract, I need to show that my speeds have been less than 50% the advertised speed, for 3 days running.

The easiest way to prove this is by sharing the Speedtest URL results, which are returned by the cli tool, such as:

…
     Upload:    20.93 Mbps (data used: 11.3 MB)
Packet Loss:     0.0%
 Result URL: https://www.speedtest.net/result/c/31dcab17-xxxx-xxxx-xxxx-xxxxxxxxxxxx

(URL obscured).

I'd love if this python script could catch and then log these URLs. That way I could import them into Loki, and correlate logs with metrics in time, in order to find the slow examples to share with my ISP.

samjewell added a commit to samjewell/speedtest-exporter that referenced this issue Jul 1, 2021
@samjewell samjewell linked a pull request Jul 2, 2021 that will close this issue
@MiguelNdeCarvalho
Copy link
Owner

Hey,

I will try to check #81 ASAP and really thanks again for your contribuition. This really could be a good feauture to the exporter itself.

Thanks again,
MiguelNdeCarvalho

@MiguelNdeCarvalho MiguelNdeCarvalho added the enhancement New feature or request label Jul 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants