Comments (10)
Hii! Can I work on this @wlach ?
Yes, please go ahead. I think there should be enough information above to get started. I won't be around consistently for the next week, but feel free to ask in #glean-dictionary if you get stuck.
from glean-dictionary.
Hi @wlach! Actually my end semester examinations are going on these days and thus I won't be able to work on this issue for the rest of the january. Though I have made some progress in this and might complete it soon once I get back to work on this. If this needs to be fixed urgently then you may assign it to someone else.
Hi Ankita, thanks for the update. I'm going to defer this to the next milestone for now, but we may need to assign to someone else in the next little bit depending on feedback. Fortunately there is no end of other things to work on in this project. 😄
from glean-dictionary.
👍 note that some probes seem to be inaccurately marked as expired, see mozilla/probe-dictionary#116
from glean-dictionary.
There are some things that need to move into place before we can tackle this, so is not a good issue for contributors. However, we should be able to tackle this in phase 1.
from glean-dictionary.
I think we can start implementing this. I think there are a few elements here:
- We need to include expiry date information in the metrics summary we use on the application page ( and ).
- Then, we can provide a checkbox on the metrics page of an application that allows the user to "Show expired metrics" (unchecked by default). If the checkbox is unticked, then we should filter all the metrics by their expiry data-- any whose expiry date is less than the current data, should not be shown. If the checkbox is ticked, we should put a pill next to any metrics that are expired that says "expired".
- On the metrics page itself, we should show the same pill saying expired.
This is analagous to the show deprecated applications on the front page:
And what we show on the application page:
from glean-dictionary.
#225 might be nice to fix before this one, it would probably reduce the work involved a bunch to make it work nicely on both the application and ping pages.
from glean-dictionary.
Hii! Can I work on this @wlach ?
from glean-dictionary.
Hi @Ankita13-code! How's it going? We were hoping to fix this issue in the next few days, if you're not available right now I might need to assign it to someone else. If you need any help with it, feel free to reach out.
from glean-dictionary.
Hi @wlach! Actually my end semester examinations are going on these days and thus I won't be able to work on this issue for the rest of the january. Though I have made some progress in this and might complete it soon once I get back to work on this. If this needs to be fixed urgently then you may assign it to someone else.
from glean-dictionary.
I'm going to work on this as I'm working on another related issue #65 and having this fixed would be really helpful.
from glean-dictionary.
Related Issues (20)
- Add an option to only show application metrics
- Link "Latest release is" links to whattrainisitnow instead of wikimo/release/calendar (which redirects)
- STMO query gen can point to tables not containing desired data HOT 5
- Debugging locally on MacOS can break due to port 5000 being used by AirPlay HOT 1
- 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
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.