There seems to be consensus around the idea this should be application defined/specific. We have two possible way forward for this. *** Proposal 1 - Allow extending the "baseline" ping *** This proposal doesn't really require us to do much. Applications using glean can simply define their product specific metrics (e.g. "release_channel") and declare them to live in all pings (i.e. `send_in_pings: default` or `send_in_pings: baseline` in the metrics.yaml file). No schema changes are required, as such metrics, being normal metrics, would be product specific and live in the ping payload. *** Proposal 2 - Introduce a ping tagging mechanism *** This would expose a new API in glean, e.g. addPingTag(tagName, tagValue)/removePingTag(tagName), that would allow adding length limited strings to the "ping_info" or "client_info" section (see [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1528787)) of all the outgoing pings. It might even be worth introducing a separate top level "tags" object for the ping, without cluttering the other ones. In case we go for the second, a lightweight proposal document will be written to iron out the details. @all - what's your take on this?
Bug 1520741 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There seems to be consensus around the idea this should be application defined/specific. We have two possible way forward for this. *** Proposal 1 - Allow extending the "baseline" ping *** This proposal doesn't really require us to do much. Applications using glean can simply define their product specific metrics (e.g. "release_channel") and declare them to live in all pings (i.e. `send_in_pings: default` or `send_in_pings: baseline` in the metrics.yaml file). No schema changes are required, as such metrics, being normal metrics, would be product specific and live in the ping payload. *** Proposal 2 - Introduce a ping tagging mechanism *** This would expose a new API in glean, e.g. `addPingTag(tagName, tagValue)`/`removePingTag(tagName)`, that would allow adding length limited strings to the "ping_info" or "client_info" section (see [this bug](https://bugzilla.mozilla.org/show_bug.cgi?id=1528787)) of all the outgoing pings. It might even be worth introducing a separate top level "tags" object for the ping, without cluttering the other ones. In case we go for the second, a lightweight proposal document will be written to iron out the details. @all - what's your take on this?