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
Speedtest Tracker uses the [Official Ookla CLI](https://www.speedtest.net/apps/cli) client to execute the speedtest. There a couple of stages the Speedtest Tracker goes through, below explains the process. 
3
+
Speedtest Tracker uses the [Official Ookla CLI](https://www.speedtest.net/apps/cli) client to execute the speedtest. There a couple of stages the Speedtest Tracker goes through, below explains the process.
4
4
5
5
{% stepper %}
6
6
{% step %}
7
-
###Started
7
+
#### Waiting
8
8
9
-
The Speedtest process is started
9
+
The speedtest run request was created but has not been started.
10
10
{% endstep %}
11
11
12
12
{% step %}
13
-
### Checking
13
+
#### Started
14
+
15
+
The speedtest process has been started by a queue worker.
16
+
{% endstep %}
17
+
18
+
{% step %}
19
+
#### Checking
14
20
15
21
The application checks for an internet connection by calling `https://icanhazip.com`
16
22
{% endstep %}
17
23
18
24
{% step %}
19
-
### Skipped \[Optional]
25
+
####Skipped \[Optional]
20
26
21
-
If you have the `SPEEDTEST_SKIP_IPS`the test will be marked as skipped as the IP returning during `Checking` matches your defined IP.
27
+
If you have the `SPEEDTEST_SKIP_IPS` the test will be marked as skipped as the IP returning during `Checking` matches your defined IP.
22
28
{% endstep %}
23
29
24
30
{% step %}
25
-
### Running
31
+
####Running
26
32
27
-
The application runs the speedtest by simply running the speedtest command. This command runs the speedtest like another other speedtest and returns the result in json format so the application an easily process it. 
33
+
The application runs the speedtest by simply running the speedtest command. This command runs the speedtest like another other speedtest and returns the result in json format so the application an easily process it.
If for various reasons the Ookla CLI returns an error, because the defined server was offline for example the tests is marked as failed. As well when the `Checking` stage fails when there is no internet. 
49
+
If for various reasons the Ookla CLI returns an error, because the defined server was offline for example the tests is marked as failed. As well when the `Checking` stage fails when there is no internet.
44
50
{% endstep %}
45
51
46
52
{% step %}
47
-
### Benchmarking
53
+
####Benchmarking
48
54
49
55
When you have thresholds set this step will evaluate the results against the threshold to determine if the test was healthy or not.
50
56
{% endstep %}
51
57
52
58
{% step %}
53
-
### Completed
59
+
####Completed
54
60
55
-
This is the end stage of the process when every step is completed the test is marked as such. 
61
+
This is the end stage of the process when every step is completed the test is marked as such.
0 commit comments