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

even mo stuff
(even mo stuff)
Line 5: Line 5:
=== Overall Project Health ===
=== Overall Project Health ===


Green - Team continues to focus on data validation. R41 is new go live target, existing work has been triaged into new milestones.  
Green - r41 is go live for unified Telemetry. All issues triaged and assigned milestones. Dev Team continues to focus on data validation.


=== Exec Summary ===
=== Exec Summary ===
Line 53: Line 53:
* created new milestones for remainder of r40 cycle, triaged bugs into the buckets
* created new milestones for remainder of r40 cycle, triaged bugs into the buckets
Ops
Ops
Perfomance
* alerts and status code trapping
*  
Performance
* spark out of mem jobs
Project management
Project management
* meeting, emails, hand waving


=== Planned for Upcoming Period ===
=== Planned for Upcoming Period ===


Engineering
Engineering
* Pipeline monitoring (tracking errors by channel and build id)
* Uplift final client changes for r40: [https://docs.google.com/spreadsheets/d/1yAJmgCGYyk1d7A41DZa653Z3u2AbH-kDWsO1vPSgbfE/edit?usp=sharing spreadsheet]
* Uplift final client changes for r40: [https://docs.google.com/spreadsheets/d/1yAJmgCGYyk1d7A41DZa653Z3u2AbH-kDWsO1vPSgbfE/edit?usp=sharing spreadsheet]
* Data validation: https://etherpad.mozilla.org/fhr-v4-validation
* Data validation: https://etherpad.mozilla.org/fhr-v4-validation
Line 66: Line 69:
* Meeting to go over Telemetry tools/microservices production deployment
* Meeting to go over Telemetry tools/microservices production deployment
* Continued work on scaling for release loads
* Continued work on scaling for release loads
* data bricks investigation (big jobs on big clusters) - cost, resourcing etc
Performance
* automate spark tel
QA
QA
* closing bugs
* closing bugs