Bug 1628029 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

We'd like to track the success rate of OS auth (bug 1194529). We can add some telemetry objects and methods to the pwmgr:mgmt_interaction event object to support this.

I propose the following objects and methods:

objects: ["osauth"]
methods: ["auth-success", "auth-failure"]

Canceling the dialog will be treated as a failure.
We'd like to track the success rate of OS auth (bug 1194529). We can add some telemetry objects and methods to the pwmgr:mgmt_interaction event object to support this.

I propose the following objects and methods:

objects: ["os_auth", "mp_auth"]
methods: ["auth_success", "auth_failure"]

Canceling will be treated as a failure.
We'd like to track the success rate of OS auth (bug 1194529). We can add some telemetry objects and methods to the pwmgr:mgmt_interaction event object to support this.

I propose the following objects and methods:

objects: ["os_auth", "mp_auth"]
methods: ["auth_pass", "auth_fail"]

Canceling will be treated as a failure.
We'd like to track the success rate of OS auth (bug 1194529). We can add some telemetry objects and methods to the pwmgr:mgmt_interaction event object to support this.

I propose the following objects and methods:

objects: ["os_auth", "mp_auth"]
methods: ["auth_pass", "auth_fail"]

Extra keys will be `skipped` which will be true when the user previously authenticated successfully and the request was made before the previous authentication expired, and `disabled` which will be true on environments where the feature is not available.

Canceling will be treated as a failure.
We'd like to track the success rate of OS auth (bug 1194529). We can add some telemetry objects and methods to the pwmgr:mgmt_interaction event object to support this.

I propose the following objects and methods:

objects: ["os_auth", "mp_auth"]
methods: ["auth_pass", "auth_fail"]

Extra keys will be `skipped` which will be true when the user previously authenticated successfully and the request was made before the previous authentication expired, and `disabled` which will be true on environments where the feature is not available.

Canceling will be treated as a failure.

The events will get recorded in the content process alongside the other events that we record.

Back to Bug 1628029 Comment 0