Open
Bug 1854569
(necko-glean)
Opened 2 years ago
Updated 8 months ago
[meta] Migrate Necko telemetry to Glean
Categories
(Core :: Networking, enhancement, P2)
Core
Networking
Tracking
()
NEW
People
(Reporter: valentin, Unassigned)
References
(Depends on 4 open bugs, Blocks 1 open bug, )
Details
(Keywords: meta, Whiteboard: [necko-triaged])
There are a lot of networking probes that are currently unavailable on Android.
Considering how important this platform is, that seems problematic.
Migrating all/the most important probes to Glean will allow us to:
- Monitor performance regressions
- Track usage of features
- Identify performance issues that only occur on Android
| Reporter | ||
Updated•2 years ago
|
Alias: necko-glean
| Reporter | ||
Comment 1•2 years ago
|
||
Note that I discovered that some probes are currently being reported on Fenix via this streaming telemetry
That should make it easier to migrate some of these probes, without having to change the actual implementation.
| Reporter | ||
Updated•2 years ago
|
Blocks: necko-tech-debt
| Reporter | ||
Comment 2•1 year ago
|
||
Bug 1877839 converted the streaming telemetry we had to real glean probes.
Going forward, we should also convert the remaining Necko probes to glean.
In order to not lose historical data when converting the probes, we should try to:
- When the glean probe definitions are compatible with the old definitions, we can use telemetry_mirror
- When the new glean definition is not compatible with the old definition, we should keep the old probe for at least 6 months before we remove it.
Updated•1 year ago
|
Assignee: nobody → sekim
Updated•1 year ago
|
Depends on: necko-ifndef-removal
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
No longer depends on: necko-ifndef-removal
Updated•8 months ago
|
Assignee: sekim → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•