Phased Approach

• Phase 1: Focus is primarily on the validation of the new architecture and delivering the metrics that Engineering needs for this.
• Phase 2: Focus is on 1) Metrics for Product Management needs and 2) 3rd Party App Developer needs

Design Approach

• Leverage the existing Desktop capabilities to send metrics to the telemetry servers.
  • Plan is to expose a DOM API for this
  • API will be C++ so that it can be leveraged both from ServiceWorkers and Content
  • Leverage the existing histograms capabilities in gecko.
  • Leverage the existing devtools capabilities in gaia and gecko
  • Design Options Considered: https://docs.google.com/document/d/1IDBRiftj_PTRE-Yu5o4EYxYMRlgN3bGutGlbCu5TgLk/edit

Phase 1 Requirements for Architecture Validations

• App Startup time
• Memory usage (exposing about:memory informations to app content, maybe under a permission)
• Reflows count / time
• Errors
• Event Loop Lag
• Async animation failures
• Security warnings
• Contract methods above the defined threshold
• Navigation Map
• Panel usage count / time spent

Bugs

Meta bug

Code

• Coming Soon...

The team

• Tamara Hills [:thills] <thills@mozilla.com>
• Russ Nicoletti [:russn] <rnicoletti@mozilla.com>

Meetings

When

• Daily Standup at 12:00 EST / 09:00 PDT

Where

• thills vidyo room.
• IRC: #gaia-telemetry #gaia

What

Standup Notes: [1]