The keys of object metric entries use language-specific casing rather than being consistent across languages. This is annoying as a developer, because working on different platforms with the same metrics requires somewhat different code. Besides that, it is very cumbersome to deal with this when trying to use ingested data in e.g. BigQuery. For instance, [this query](https://sql.telemetry.mozilla.org/queries/103617) merges desktop and Android data: the metrics are identical on both platforms, however the data ends up being incompatible because of the differently named keys.
Bug 1931891 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The keys of object metric entries use language-specific casing rather than being consistent across languages. This is annoying as a developer, because working on different platforms with the same metrics requires somewhat different code. Besides the client code, it is very cumbersome to deal with this when trying to use ingested data in e.g. BigQuery. For instance, [this query](https://sql.telemetry.mozilla.org/queries/103617) merges desktop and Android data: the metrics are identical on both platforms, however the data ends up being incompatible because of the differently named keys.