Telemetry for bad key state in AutofillCrypto
Categories
(Firefox for Android :: Autofill, task)
Tracking
()
People
(Reporter: gl, Unassigned)
Details
From github: https://github.com/mozilla-mobile/android-components/issues/10122.
When lost/corrupted/etc key state is detected, these events should be recorded in our telemetry for monitoring/analysis.
Two alternatives to this:
- do nothing; but, then we don't know if managed keys are being lost/corrupted
- send artificial exceptions to Sentry; as a crash tracking system, Sentry really isn't well-suited for tracking these kinds of metrics over time though; I don't want to add even more noise to what's already a hard-to-navigate environment.
So we're basically looking at emitting some glean metrics - either directly, or in Fenix via Facts. Seems like doing this directly in the component, and not forcing the consuming application to deal with telemetry is the better approach here.
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
|
||
Comment 1•3 years ago
|
||
The severity field is not set for this bug.
:cpeterson, could you have a look please?
For more information, please visit auto_nag documentation.
|
||
Updated•3 years ago
|
|
||
Comment 2•3 years ago
|
||
Closing this because the telemetry was asked 2 years ago and no action has taken up to this date. We can open later on in case of further requests on the issue.
Description
•