Garvan Keeley

Are the project changes in this patch intentional?

Currently, the lib is intended for • once-per-session Core Ping • user interaction rate limited (i.e. primarily user tap-initiated) UI event telemetry. Any high-rate telemetry, or telemetry on app events...

Will do, you are correct, all calls are main-thread async. They can result in main thread contention if called at excessive rate.

See also https://github.com/mozilla-mobile/telemetry-ios/issues/12

Use event counting in https://github.com/mozilla-mobile/telemetry-ios/issues/70 And just set "crash": 0/1

@justindarc I am thinking of working on this next. It appears straightforward to wrap the entire lib to run on a single concurrent background queue (no big refactor is needed...

Where did you see this? I don't see any (null) currently I tried ``` select distinct(default_mail_client), count(default_mail_client) as default_mail_client_count from telemetry.mobile_clients_v2 where os = 'iOS' and buildid='7227' group by default_mail_client...

I would like if we added a synchronized array that acts as a queue to rate limit inputs to the lib while we add this.

@fbertsch any more info on this?

Dashboard for monitoring missing ping sequence numbers: https://sql.telemetry.mozilla.org/dashboard/core-ping-sequence-numbers-count-per-day The docs on creating the above graph: : https://docs.telemetry.mozilla.org/cookbooks/realtime_analysis_plugin.html Recommended we add `Fields[docType] == ‘core’` to isolate to core pings. Additional useful...