As a privacy safeguard, we are currently only reporting on the slow execution of prepared SQL statements. Consequently we are missing a lot of time-consuming SQL created from dynamic strings. We should investigate collecting metrics on such SQL and perhaps reporting only its JavaScript call stack instead of the actual SQL string.

Comment on attachment 602352 [details] [diff] [review] about-telemetry change s/fullSlowSQL/debugSlowSQL/. I'm still pondering rest of the stuff

Comment on attachment 602234 [details] Sample about:telemetry output and corresponding Telemetry Ping report I'm not sure of utility of telling addon dbs apart from non-addon dbs within the ping. For now we should report a cumulative number like "dynamic query on x.sqlite" We should also add a toolkit.telemetry.debugSlowSQL=false pref and gate private sql recording on that.

Comment on attachment 602230 [details] [diff] [review] Report full SQL strings locally & aggregate private stats for Telemetry, v1 r- based on irc discussion

Comment on attachment 603909 [details] [diff] [review] Report full SQL strings locally & aggregate private stats for Telemetry, v2 AddonDb -> TrackedDB + fullSql.AppendPrintf(" /* addon DB %s */", dbName.BeginReading()); -- is the proper comment prefix for SQL. s/addon/untracked/