Confirmed users
381
edits
Performance/Telemetry: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Telemetry allows developers to receive aggregate data of browser health in the field ([https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry docs]). | Telemetry allows developers to receive aggregate data of browser health in the field ([https://developer.mozilla.org/en/XPCOM_Interface_Reference/nsITelemetry docs]). | ||
Note currently Telemetry info is not present sent by the crash reporter. | |||
== Telemetry gotchas == | == Telemetry gotchas == | ||
| Line 9: | Line 11: | ||
= Threading = | = Threading = | ||
Histograms should always be accessed from the same thread as they are created. Creating a new histogram (or obtaining an existing one) is protected by a lock. However accumulating data is not thread-safe. | Histograms should always be accessed from the same thread as they are created. Creating a new histogram (or obtaining an existing one) is protected by a lock. However accumulating data is not thread-safe. | ||
= Timing Attacks = | |||
Probes must not appear in code paths that are sensitive to timing attacks on passwords/keys. | |||
= Addons = | |||
Addons must not add probes because we cannot evaluate them for privacy problems. Addons introduce a security liability of having Firefox send potentially private information to our servers. | |||
= Data Gathered = | = Data Gathered = | ||