The failure can be determined via the detailed failure information that is already recorded in telemetry histograms. Regretfully, telemetry scalars don't support multiple values in one session so if an update failed before restarting the next attempt would overwrite the failure due to how scalars work. Since there are multiple fall backs for the download phase I am adding a bitfield value so it is possible to determine which download methods were tried.
Bug 1528278 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The failure can be determined via the detailed failure information that is already recorded in telemetry histograms though intervals aren't included in this. Regretfully, telemetry scalars don't support multiple values in one session so if an update failed before restarting the next attempt would overwrite the failure due to how scalars work. Since there are multiple fall backs for the download phase I am adding a bitfield value so it is possible to determine which download methods were tried.
The failure can be determined via the detailed failure information that is already recorded in telemetry histograms though intervals aren't included in this. Regretfully, telemetry scalars which are needed for the intervals don't support multiple values in one session so if an update failed before restarting the next attempt would overwrite the failure due to how scalars work. Since there are multiple fall backs for the download phase I am adding a bitfield value so it is possible to determine which download methods were tried.