Unified Telemetry/Status reports/July 17 2015: Difference between revisions

Line 64: Line 64:


Engineering
Engineering
* Pipeline monitoring (tracking errors by channel and build id)
* Client
* Uplift final client changes for r40: [https://docs.google.com/spreadsheets/d/1yAJmgCGYyk1d7A41DZa653Z3u2AbH-kDWsO1vPSgbfE/edit?usp=sharing spreadsheet]
** Do code reviews for deletion pings and choices info bar
* Data validation: https://etherpad.mozilla.org/fhr-v4-validation
** Pending ping cleanup
* Targeting 40r9 as next major milestone to have bulk of validation work completed.
** Investigate count discrepancies between "main" pings and "saved session" pings
* Pipeline
** Continue with scaling work
** Monitoring work for Telemetry data
** Investigate executive stream discrepancies
** Bug fixes
* Data validation
** Join corresponding v2 data to v4 nightly clients data set
** Continue writing callbacks that look at other measures
** Breadth first, do a first pass at most validations and flag big issues
** Deep dive on missing subsessions as it may indicate a client bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1171268
* Data continuity
** Document strategy for executive dashboards with v2 + v4 data
Ops
Ops
* Meeting to go over Telemetry tools/microservices production deployment
* Continued work on scaling for release loads
* data bricks investigation (big jobs on big clusters) - cost, resourcing etc
* data bricks investigation (big jobs on big clusters) - cost, resourcing etc
Performance
* automate spark
QA
QA
* closing bugs
* closing bugs
Line 80: Line 88:
Project Management
Project Management
* Finish triage of bugs
* Finish triage of bugs
*remainder of release tasks scheduled
* remainder of release tasks scheduled


=== Outstanding requests not yet road mapped into a release ===
=== Outstanding requests not yet road mapped into a release ===
Confirmed users
539

edits