1834792 - Make Glean ping throttling limits configurable via Nimbus

Status: RESOLVED FIXED

(Toolkit :: Telemetry, task, P2)

Description

[Chris H-C :chutten]

Current numbers suggest that PingCentre Replacement with Glean shouldn't blow out our budget for sending frequency:

• Per docs we attempt upload of 15 pings per 60s interval. With bug 1647630 we will be able to configure both the number of the pings and the length of the interval.
• Ping volumes for all namespaces from PingCentre: most days most clients send fewer than 15 pings. 99th %ile is at 186/day which would take 13 intervals of 60s to clear with current configuration

So this should be fine... but we don't want to lose data.

This bug is about exposing the new configuration options from bug 1647630 to Nimbus so that, should we find ourselves missing some data (which we will detect on the to-be-build pingcentre replacement system validation dashboard), we can remotely loosen our throttling restrictions.

Comment 1

[Perry McManis [:perry.mcmanis]]

Attachment: Bug 1834792 - Make Glean ping throttling limits configurable via Nimbus r?TravisLong

Depends on D182598

Comment 2

[Perry McManis [:perry.mcmanis]]

Attachment: Data Review Request

Data review request:

Comment 3

[Perry McManis [:perry.mcmanis]]

Travis I have a data review request for you please and thank you!

Comment 4

[Travis Long [:travis_]]

Comment on attachment 9342437 [details]
Data Review Request

Data Review

1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary.

2. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, through the telemetry preferences in the application settings.

3. If the request is for permanent data collection, is there someone who will monitor the data over time?

Permanent collection to be monitored by [e-mail] with glean-team as a fallback

4. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 1, Technical data

5. Is the data collection request for default-on or default-off?

Default-on

6. Does the instrumentation include the addition of any new identifiers (whether anonymous or otherwise; e.g., username, random IDs, etc. See the appendix for more details)?

No

7. Is the data collection covered by the existing Firefox privacy notice?

Yes

8. Does the data collection use a third-party collection tool?

No

Result

data-review+

Comment 5

[Travis Long [:travis_]]

FYI, when you attach the data-review request, you should select the ? next to the data-review option and then enter a data-steward's email in the field next to it rather than using needinfo.

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:perry.mcmanis, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Comment 7

[Travis Long [:travis_]]

I think this is waiting on an update to Glean in m-c, which has been held up for other reasons. See also https://bugzilla.mozilla.org/show_bug.cgi?id=1840044

Comment 8

[Jan-Erik Rediger [:janerik]]

More precisely it's even waiting on yet unreleased changes.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/2c4954ceb46a
Make Glean ping throttling limits configurable via Nimbus r=TravisLong,supply-chain-reviewers

Comment 10

[Natalia Csoregi [:nataliaCs]]

https://hg.mozilla.org/mozilla-central/rev/2c4954ceb46a

Comment 11

[Jan-Erik Rediger [:janerik]]

Note that as written the gleanMaxPingsPerMinute can currently not be experimented on properly, due to the lack of isEarlyStartup: true for the feature which is required for the C++ API to work.
This is handled in bug 1848331