๐Ÿ‡
Speedtest Tracker
  • Introduction
  • Features
  • Changelog
  • ๐Ÿš€Getting Started
    • Installation
      • Using Docker Compose
      • Using Docker
      • Using Kubernetes
      • Using QNAP
      • Using Synology
      • Using Unraid
    • Environment Variables
    • Database Drivers
  • ๐Ÿ†˜Help
    • Error Messages
    • Frequently Asked Questions
  • ๐Ÿ”‘Security
    • Authentication
    • Authorization
    • Encryption
  • โš™๏ธSettings
    • Data Integrations
      • InfluxDB v2
    • Notifications
      • Database
      • Mail
      • Webhook
  • ๐Ÿ‘€Other
    • Speedtest Process
    • Proxies
      • Cloudflare Tunnel (Zero Trust)
      • Traefik
      • Tailscale
    • Caching
    • Commands
    • Data Dictionary
    • Embed Dashboard
    • Health Check
    • Community Projects
  • ๐Ÿ–ฅ๏ธAPI
    • Authorization
    • Responses
      • Results
      • Speedtests
      • Servers
      • Stats
      • Models
  • ๐ŸคนContributing
    • Development Environment
  • ๐Ÿ”—More
    • Source Code
    • Releases
    • Update the Docs
    • About Me
    • Donate
Powered by GitBook
On this page
Edit on GitHub
  1. Other

Speedtest Process

PreviousWebhookNextProxies

Last updated 5 days ago

Speedtest Tracker uses the client to execute the speedtest. There a couple of stages the Speedtest Tracker goes through, below explains the process.

1

Waiting

The speedtest run request was created but has not been started.

2

Started

The speedtest process has been started by a queue worker.

3

Checking

The application checks for an internet connection by calling https://icanhazip.com

4

Skipped [Optional]

If you have the SPEEDTEST_SKIP_IPS the test will be marked as skipped as the IP returning during Checking matches your defined IP.

5

Running

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.

speedtest -accept-license --accept-gdpr --format=json

Or when you have defined a server id:

speedtest -accept-license --accept-gdpr --format=json --server-id=YOURSERVERID
6

Failed

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.

7

Benchmarking

When you have thresholds set this step will evaluate the results against the threshold to determine if the test was healthy or not.

8

Completed

This is the end stage of the process when every step is completed the test is marked as such.

๐Ÿ‘€
Official Ookla CLI