iperf3 sensor integration allows you to measure network bandwidth performance against a private or public Iperf3 server.
Enabling this integration will automatically create the Iperf3 sensors for the monitored conditions (below). By default, it will run every hour. The user can change the update frequency in the configuration by defining the
scan_interval for a Iperf3 test to run.
This integration requires the
iperf3 command to be installed on your OS. Please, refer to the official Iperf3 documentation for installation instructions.
To add the
iperf3 sensor to your installation, add the following to your
Once per hour, on the hour (default):
# Example configuration.yaml entry
- host: iperf.he.net
Sensors to display in the frontend.
Minimum time interval between updates. Supported formats:
scan_interval: 'HH:MM' and Time period dictionary (see example below).
Configuration variables (host):
Specify the test duration in seconds. Default is 10 and the valid range is from 5 to 10.
Specify the number of concurrent streams to connect to the server. Default is 1 and the valid range is from 1 to 20.
Specify the protocol to be used on the test. Default is TCP and the valid values are TCP or UDP. If your Iperf3 server is located in the Internet, consider to use TCP instead of UDP. If the protocol is set to use UDP, the sensor may not get updated due to package retransmission issues due to its nature.
# At least one of these must be specified:
The frequency when the test will be automatically triggered can be adjusted by setting the value
scan_interval in seconds.
Parallel streams can help in some situations. As TCP attempts to be fair and conservative, you may consider increasing the
parallel attribute. Use this value with careful and refer to Iperf3 man page for more information.
You can use the service
sensor.iperf3_update to trigger a manual speed test for all sensors. Iperf3 has its own service call that allow to perform a speed test on a particular entity.
Once loaded, the
iperf3 integration will expose a service (
iperf3.speedtest) that can be called to run a speed test on demand. This can be useful if you have enabled manual mode.
| Service data attribute | Description |
host | String that point at a configured
configuration.yaml. Otherwise, tests will be run against all configured hosts.
Example Service data: