connection_health.changed_to_no_signal
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.
Metric of type event. Sent in the daemonsession, vpnsession pings.
The event category is connection_health
and event
name is changed_to_no_signal.
Source | mozilla-mobile/mozilla-vpn-client/src/telemetry/metrics.yaml#L741 |
Code Search | connection_health.changed_to_no_signal |
Metric sampling
Not Sampled | This metric is not currently affected by any sampling configuration and is operating based on its defaults in the metrics.yaml file |
Sampling Configuration Snippet | Click the button to copy a snippet for use in a Mozilla Experimenter configuration. |
Metadata
Data Sensitivity |
|
Lifetime | ping |
First Added | 2024-03-18 16:01:04 |
Bugs | |
Data reviews | |
Notification Emails | |
Expires | 2025-04-15 |
Commentary
No commentary for this metric, add some?
Access
GLAM | This application is not supported by GLAM. |
Looker | |
BigQuery | In
mozillavpn.daemonsession
and mozillavpn.daemonsession
>
mozilla_vpn.daemonsession 🔒 (event.category= connection_health and event.name=changed_to_no_signal ) |
Data Catalog
| metrics.event.connection_health_changed_to_no_signal 🔒 |
STMO |