Mozilla VPN

The optional Android specific SDK version of the software running on this hardware device.

The build identifier generated by the CI system (e.g. "1234/A"). If the value was not provided through configuration, this metric gets set to Unknown.

The channel the application is being distributed on.

The user visible version string (e.g. "1.0.3"). If the value was not provided through configuration, this metric gets set to Unknown.

The architecture of the device, (e.g. "arm", "x86").

The date & time the application was built.

A UUID uniquely identifying the client.

The connection status changed to no signal. This event is recorded in both main application and daemon. The logic and cadence of health checks for each of these is not the same. A no signal event happens when the connection is showing issues, and a silent switch will not address the issue. Or when the connection is showing issues and there have been previous silent switches which did not address the issue.

(iOS only) The connection status changed to pending. This event is recorded in daemon. Pending status is when the app is first started or when there is no internet.

The connection status changed to stable. This event is recorded in both main application and daemon. The logic and cadence of health checks for each of these is not the same. Stable status is when the app is not in a no signal or unstable connection state.

The connection status changed to unstable. This event is recorded in both main application and daemon. The logic and cadence of health checks for each of these is not the same. An unstable event happens when the connection is showing issues, but silent switches may still address the issue.

The amount of data received through the VPN tunnel. This metric is accumulated periodically on a 3hr interval while the VPN is turned on. This metric is not collected on iOS. > Note: This metric is recorded on the vpnsession ping for > desktop platforms and on the daemonsession ping for mobile platforms.

The amount of data sent through the VPN tunnel. This metric is accumulated periodically on a 3hr interval while the VPN is turned on. This metric is not collected on iOS. > Note: This metric is recorded on the vpnsession ping for > desktop platforms and on the daemonsession ping for mobile platforms.

Count of times that the connection health check results in no signal. The health check counters must not be considered as markers of time. There is a possible situation in the health check (which calls the telemetry) which frequently results in more than one count per second. The situation: A health check is conducted because a network check did not return, and milliseconds later that network check returns and another health check is started because of the return.

Time spent in no signal state. Only collected on desktop for vpnsession, as mobile apps frequently are relaunched during VPN sessions. It is collected in daemonsession for mobile clients.

(iOS only) Count of times that the connection health check is in pending. The health check counters must not be considered as markers of time. There is a possible situation in the health check (which calls the telemetry) which frequently results in more than one count per second. The situation: A health check is conducted because a network check did not return, and milliseconds later that network check returns and another health check is started because of the return.

(iOS only) Time spent in pending state.

The iOS PingAnalyzer returned an error.

Count of times that the connection health check succeeds. The health check counters must not be considered as markers of time. There is a possible situation in the health check (which calls the telemetry) which frequently results in more than one count per second. The situation: A health check is conducted because a network check did not return, and milliseconds later that network check returns and another health check is started because of the return.

Time spent in stable state. Only collected on desktop for vpnsession, as mobile apps frequently are relaunched during VPN sessions. It is collected in daemonsession for mobile clients.