Archives/iceraven-browser
2
0
Fork 0
mirror of https://github.com/fork-maintainers/iceraven-browser synced 2024-11-09 19:10:42 +00:00
Code Issues Releases Wiki Activity
2380d51808
iceraven-browser/app/pings.yaml

54 lines
2.1 KiB
YAML
Raw Normal View History

Generate the `activation` ping and send it with Glean (#1707) This fetches the Google Advertising ID, salts it and then applies hashing before sending a ping with it, at startup. Hashing and salting are used in order to prevent ourselves to correlate advertising IDs from the same user running different products we own off a single device. We will never send the client_id and the Google Advertising ID in the same ping.
2019-05-03 14:40:22 +00:00
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.
Fix glinter errors
2020-04-15 17:04:27 +00:00
---
Bug 1689162: Update Glean metrics.yaml schema (#18683)
2021-03-29 15:53:45 +00:00
$schema: moz://mozilla.org/schemas/glean/pings/2-0-0
Generate the `activation` ping and send it with Glean (#1707) This fetches the Google Advertising ID, salts it and then applies hashing before sending a ping with it, at startup. Hashing and salting are used in order to prevent ourselves to correlate advertising IDs from the same user running different products we own off a single device. We will never send the client_id and the Google Advertising ID in the same ping.
2019-05-03 14:40:22 +00:00
activation:
Fix glinter errors
2020-04-15 17:04:27 +00:00
description: |
This ping is intended to provide a measure of the activation of mobile
products. It's generated when Fenix starts, right after Glean is
initialized. It doesn't include the client_id, since it might be reporting
an hashed version of the Google Advertising ID.
Generate the `activation` ping and send it with Glean (#1707) This fetches the Google Advertising ID, salts it and then applies hashing before sending a ping with it, at startup. Hashing and salting are used in order to prevent ourselves to correlate advertising IDs from the same user running different products we own off a single device. We will never send the client_id and the Google Advertising ID in the same ping.
2019-05-03 14:40:22 +00:00
include_client_id: false
Add pings.yaml metadata
2019-05-14 13:56:19 +00:00
bugs:
Update bug numbers to URLs for activation ping Earlier versions of Glean supported bug numbers of the metadata, but this causes ambiguity, particularly for Fenix where issues exist in both Bugzilla and Github. This just updates the Bugzilla numbers to full URLs. We made the use of numbers an error sometime ago, but neglected to enforce this on "pings" in addition to "metrics". A future version of `glean_parser` [1] will make this an error and this will set Fenix up to be ready for that. [1] https://github.com/mozilla/glean_parser/pull/262
2021-01-14 16:20:34 +00:00
- https://bugzilla.mozilla.com/1538011/
- https://bugzilla.mozilla.com/1501822/
Add pings.yaml metadata
2019-05-14 13:56:19 +00:00
data_reviews:
- https://github.com/mozilla-mobile/fenix/pull/1707#issuecomment-486972209
notification_emails:
For FNX-22820: uplift expired telemetry and update glean notification email address (#20074) * For #19923: renew telemetry probes (#19924) * Update glean notification emails to new email group (#20070)
2021-06-21 17:05:17 +00:00
- android-probes@mozilla.com
For #7295 - Adds new custom ping: 'installation'
2020-02-04 10:52:10 +00:00
For #11392: Rename Installation ping to FirstSession (#11869)
2020-06-25 17:06:26 +00:00
first-session:
Fix glinter errors
2020-04-15 17:04:27 +00:00
description: |
For #11392: Rename Installation ping to FirstSession (#11869)
2020-06-25 17:06:26 +00:00
This ping is intended to capture the source of the app install
on the first session.
For #9136: Send all adjust properties to glean (#9253)
2020-03-20 17:06:55 +00:00
include_client_id: true
For #7295 - Adds new custom ping: 'installation'
2020-02-04 10:52:10 +00:00
bugs:
For #7295 - Removes some incorrect data-review links
2020-02-06 13:48:21 +00:00
- https://github.com/mozilla-mobile/fenix/issues/7295
For #7295 - Adds new custom ping: 'installation'
2020-02-04 10:52:10 +00:00
data_reviews:
For #7295 - Adds more documentation for the installation metrics
2020-02-14 22:09:14 +00:00
- https://github.com/mozilla-mobile/fenix/pull/8074#issuecomment-586512202
For #7295 - Adds new custom ping: 'installation'
2020-02-04 10:52:10 +00:00
notification_emails:
For FNX-22820: uplift expired telemetry and update glean notification email address (#20074) * For #19923: renew telemetry probes (#19924) * Update glean notification emails to new email group (#20070)
2021-06-21 17:05:17 +00:00
- android-probes@mozilla.com
For #8803: add StartupTimeline ping type and framework_start metrics.
2020-03-31 22:56:32 +00:00
startup-timeline:
Update Android Components version to 41.0.20200512130104 🎲🎲 (#10600) * Update GLEAN metrics and ping formatting * Update Android Components version to 41.0.20200512130104.
2020-05-12 18:52:58 +00:00
description: |
For #8803: add StartupTimeline ping type and framework_start metrics.
2020-03-31 22:56:32 +00:00
This ping is intended to provide an understanding of startup performance.
For #17972: add client id to startup-timeline ping, update docs. This addresses the root problem we're experiencing for this issue - data not showing up in GLAM.
2021-02-18 03:34:10 +00:00
In addition to being captured on real devices, the ping data was prematurely
optimized into this separate ping to be isolated from other metrics to be
more easily captured by performance testing automation but that hasn't
happened in practice. We would have removed it but implementation
details don't make that possible:
https://github.com/mozilla-mobile/fenix/issues/17972#issuecomment-781002987
include_client_id: true
For #8803: add StartupTimeline ping type and framework_start metrics.
2020-03-31 22:56:32 +00:00
bugs:
- https://github.com/mozilla-mobile/fenix/issues/8803
For #17972: add client id to startup-timeline ping, update docs. This addresses the root problem we're experiencing for this issue - data not showing up in GLAM.
2021-02-18 03:34:10 +00:00
- https://github.com/mozilla-mobile/fenix/issues/17972
For #8803: add StartupTimeline ping type and framework_start metrics.
2020-03-31 22:56:32 +00:00
data_reviews:
For #8803 - post: update metrics & pings data review URL.
2020-04-16 23:15:35 +00:00
- https://github.com/mozilla-mobile/fenix/pull/9788#pullrequestreview-394228626
For #17972: split frameworkStart into two metrics. We do this in order to make it easier to analyze in GLAM: see the metric descriptions for more details. Additionally, we change the time unit to milliseconds to make it easier to analyze in GLAM.
2021-02-18 04:13:45 +00:00
- https://github.com/mozilla-mobile/fenix/pull/18043#issue-575389284
For #8803: add StartupTimeline ping type and framework_start metrics.
2020-03-31 22:56:32 +00:00
notification_emails:
- perf-android-fe@mozilla.com
For #17972: add client id to startup-timeline ping, update docs. This addresses the root problem we're experiencing for this issue - data not showing up in GLAM.
2021-02-18 03:34:10 +00:00
- mcomella@mozilla.com
Reference in New Issue Copy Permalink