Please add policies.is_enterprise to baseline ping
Categories
(Firefox :: Enterprise Policies, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox148 | --- | fixed |
People
(Reporter: kwindau, Assigned: mkaply)
Details
Attachments
(1 file)
Would someone be able to add policies.is_enterprise to the baseline ping? It's currently on metrics and events only right now, and if it were on the baseline ping, it would help us with being able to add "is enterprise" to the baseline active users aggregates table, which is a request from Romain Testard.
https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/policies_is_enterprise
Comment 1•9 months ago
|
||
This is slightly complicated by policies.is_enterprise having ping lifetime (to match the Scalar it was migrated from). I'm guessing it would be intended to have lifetime: application were it implemented today with Glean.
Passing to Enterprise Policies who own the collection to decide how to proceed.
| Assignee | ||
Comment 2•9 months ago
|
||
It is lifetime: application?
https://searchfox.org/firefox-main/source/toolkit/components/enterprisepolicies/metrics.yaml#52
Comment 3•9 months ago
|
||
Oh, it is! Goodness, how'd I miss that. I even wrote it. I blame.... DST ending. Yeah, that must've been it.
| Assignee | ||
Comment 4•9 months ago
|
||
Where are the values for send_in_pings documented?
Comment 5•9 months ago
•
|
||
A few places: https://mozilla.github.io/glean/book/user/pings/custom.html#sending-metrics-in-a-custom-ping and https://mozilla.github.io/glean/book/reference/yaml/metrics.html#send_in_pings are the two that I'd expect folks to find first
| Assignee | ||
Comment 6•9 months ago
|
||
So I guess it's just a matter of adding baseline to our send_in_pings?
Will that affect any other reporting?
Comment 7•9 months ago
|
||
It will not. But it will make each "baseline" ping a little bit larger. Those pings can be submitted quite frequently, so we have a vested interest in keeping it as small as possible, so you may need to no_lint a rule to convince glean_parser that you've weighed the weight and found it worth it for the benefit.
Comment 8•9 months ago
|
||
The severity field is not set for this bug.
:mkaply, could you have a look please?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 9•7 months ago
|
||
But it will make each "baseline" ping a little bit larger. Those pings can be submitted quite frequently, so we have a vested interest in keeping it as small as possible, so you may need to no_lint a rule to convince glean_parser that you've weighed the weight and found it worth it for the benefit.
Am I allowed to make that determination? Do I need outside input?
Comment 10•7 months ago
|
||
That's a rather unfortunately loaded question of the form "Is the cost of this worth the benefit?" paired with "Who owns this data/is responsible for making that decision?" which we don't have answers for.
So for this case in particular... eh, might as well go for it. If it ends up not being worth the cost, we can turn it off later with Server Knobs.
| Assignee | ||
Comment 11•7 months ago
|
||
Updated•7 months ago
|
Comment 12•7 months ago
|
||
Comment 13•7 months ago
|
||
| bugherder | ||
Updated•7 months ago
|
Description
•