Telemetry/Outreachy:HealthPing: Difference between revisions
Gfritzsche (talk | contribs) m (typo) |
Gfritzsche (talk | contribs) m (add #outreachy) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
The collected data is submitted to our servers in [http://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/concepts/pings.html pings], the most critical being the [https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/data/main-ping.html "main" ping]. | The collected data is submitted to our servers in [http://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/concepts/pings.html pings], the most critical being the [https://gecko.readthedocs.org/en/latest/toolkit/components/telemetry/telemetry/data/main-ping.html "main" ping]. | ||
While we have active monitoring and dashboards based on the "main" ping, we currently can't track any failures to send this ping. | While we have active monitoring and dashboards based on the "main" ping, we currently can't track any failures to send this ping. | ||
To solve this we plan to add a minimal "health" ping, small-sized and going through minimal client-code, that will be submitted on failure scenarios like internal client errors or rejected submissions. | To solve this we plan to add a minimal "health" ping, small-sized and going through minimal client-code, that will be submitted on failure scenarios like internal client errors or rejected submissions. | ||
| Line 25: | Line 26: | ||
* validating incoming data | * validating incoming data | ||
* working with team members to make the data available in our re:dash instance | * working with team members to make the data available in our re:dash instance | ||
== Getting started == | |||
First you should get [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_build Firefox built & running]. | |||
Mentored bugs in Telemetry can be [https://www.joshmatthews.net/bugsahoy/?internals=1&unowned=1 found here], but you can also take on starter bugs from [https://www.joshmatthews.net/bugsahoy/?ff=1&internals=1&sync=1&unowned=1 other typical Firefox bugs]. | |||
Feel free to reach out for recommendations on good bugs. | |||
Once you found a suitable bug, leave a comment stating that you want to work on it. | |||
When you made the changes you need to [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch submit a patch]. | |||
More details can be found in our [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction developer guide]. | |||
== Contact == | |||
To get in touch you can: | |||
* reach out [https://mozillians.org/en-US/u/gfritzsche/ per mail] | |||
* connect on [[IRC|Mozilla IRC]] in the #outreachy or #telemetry channel. | |||
== Resources == | == Resources == | ||
* Mentor: [https://mozillians.org/en-US/u/gfritzsche/ Georg Fritzsche] | |||
* [[Telemetry|Telemetry project page]] | * [[Telemetry|Telemetry project page]] | ||
* View your Firefox Telemetry data at <code>about:telemetry</code> | * View your Firefox Telemetry data at <code>about:telemetry</code> | ||
* [https://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/index.html Telemetry client documentation] | * [https://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/index.html Telemetry client documentation] | ||
* [https://telemetry.mozilla.org/ Public Telemetry dashboards] | * [https://telemetry.mozilla.org/ Public Telemetry dashboards] | ||
* IRC: irc.mozilla.org, #telemetry | * [[IRC]]: irc.mozilla.org, #outreachy & #telemetry | ||
Latest revision as of 12:59, 6 March 2017
As you use Firefox, Telemetry measures and collects non-personal information, such as performance, hardware, usage and customizations. It then sends this information to Mozilla on a daily basis, where it is used to enable data-driven product decisions and engineering efforts.
The collected data is submitted to our servers in pings, the most critical being the "main" ping.
While we have active monitoring and dashboards based on the "main" ping, we currently can't track any failures to send this ping. To solve this we plan to add a minimal "health" ping, small-sized and going through minimal client-code, that will be submitted on failure scenarios like internal client errors or rejected submissions.
Project goals
This project is about implementing fundamental health monitoring of our client Telemetry.
- Make it possible to monitor submission failures of richer pings.
- Make it possible to monitor failures to generate richer pings.
Project details
In Firefox, Telemetry is mostly implemented in toolkit/components/telemetry/. For this project, you will need:
- JavaScript for the Firefox implementation
- Python for validating incoming data using PySpark
This project will involve:
- working with team members on the design of the health reporting
- implementing the new design on the client, including test coverage
- working with QA on a test plan for the reporting
- validating incoming data
- working with team members to make the data available in our re:dash instance
Getting started
First you should get Firefox built & running.
Mentored bugs in Telemetry can be found here, but you can also take on starter bugs from other typical Firefox bugs. Feel free to reach out for recommendations on good bugs. Once you found a suitable bug, leave a comment stating that you want to work on it.
When you made the changes you need to submit a patch.
More details can be found in our developer guide.
Contact
To get in touch you can:
- reach out per mail
- connect on Mozilla IRC in the #outreachy or #telemetry channel.
Resources
- Mentor: Georg Fritzsche
- Telemetry project page
- View your Firefox Telemetry data at
about:telemetry - Telemetry client documentation
- Public Telemetry dashboards
- IRC: irc.mozilla.org, #outreachy & #telemetry