Measure web endpoint latency over the SIM connection
Request a URL several times over the SIM's data connection and measure its mean response time and failure rate.
Of the latency checks, HTTP Ping comes closest to what a user feels when reaching your service over the mobile network: it times real web requests, not network packets. Use Ping for raw network latency, and API Call when you also need to check what the response contains.
Parameters
| Parameter | Required | Description |
|---|---|---|
| Host | Yes | URL to ping, for example http://kapptivate.com. |
| Ping count | No | Number of requests. Default: 10. |
| Ignore SSL certificate | No | Skip certificate verification. Default: off. |
| HTTP Ping should fail | No | Invert the verdict. |
Plus the shared connection settings and DNS override (command.override_dns, command.dns).
Results and metrics
In the action report (result):
| Field | Description |
|---|---|
rtt_mean | Mean response time. |
packet_loss_pct | Percentage of failed requests. |
ping_count | Number of requests. |
dns_server | DNS servers used. |
duration | Total execution time in seconds. |
In Analytics, each run feeds the HTTP ping measurement with rtt_seconds, packet_loss_percent, and duration_seconds, tagged by status, APN, DNS server, antenna, and access technology.
What's next?
Last updated on