Comments (2)
The idea of data annotations ("Probe X was affected in way Y from Date 1 to Date 2 on channels Cs and versions Vs, see bugs Bs") usually gets bogged down in how to make it queryable, or at least programmatically accessible so that any time series in re:dash or wherever could grab it. This results in the problem being pushed to the edge: each visualization comes up with its own way of handling it (which is okay, and probably preferable, but it kills the idea of any central annotation dataset).
If we ignored the machine readability of it and instead added them like comments to probes' details views on the probe dictionary (either by giving the probe dictionary its own storage or by putting it into the probe scraper output directly) then we might shrink this problem to something manageable. By relying on analysts' brains to filter the relevant parts and keep them around in case they're relevant to the analysis at hand, we get a lot of flexibility for less cost in building the system.
I like it.
from glean-dictionary.
I'm not sure if/when we'll do this for the glean dictionary, but if it's going to happen anywhere, it's going to happen here. 😄
from glean-dictionary.
Related Issues (20)
- Remove obsolete pings and/or metrics
- "Code Search" queries are not precise/helpful HOT 1
- `includes_client_id` probably ought to be exposed in ping details pages
- Add "i" information link for "Sampled" column on metric list page HOT 3
- Metric detail page shows "undefined" for some metric sampling configurations
- play_store_attribution.install_referrer_response Missing Looker Link
- Make Server Knobs configuration snippet copy button more obvious
- Probe queries can return apparently unrelated probes
- Consider adding metric name to page title HOT 3
- pytest >= 8 breaks tests (`PytestDeprecationWarning`)
- Experiment data for Fenix metric sampling isn't being picked up from Experiment API
- Add a way to document OHTTP pings, and support their lack of metadata
- Not all event metrics on "events" pings get event monitoring dashboard links
- Change autogenerated SQL to use `events_stream` tables
- Events stream queries should filter on sample_id
- [feature] App-specific debug instruction
- Reevaluate data_sensitivity handling and impact on downstream tools
- Implement a cookie banner
- Update searchfox links for Android to point to mozilla-central
- Consider hiding or annotating metrics sent in pings not defined in the application
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from glean-dictionary.