Open Bug 679522 Opened 14 years ago Updated 7 years ago

Display distribution of simple values

Categories

(Mozilla Metrics :: Frontend Reports, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

Moved to JIRA

People

(Reporter: taras.mozilla, Unassigned)

Details

(Whiteboard: [JIRA BIV-110] [Telemetry:P1])

Attachments

(1 file)

Attached image mockup
Would be nice to both have an idea of how simpleMeasurements are distributed and to be able to filter based on them
This mockup is very interesting, but it seems to be focused on the distribution of submissions per build and selection of builds rather than on simple measurements. Did it get posted to the wrong bug?
(In reply to Daniel Einspanjer :dre [:deinspanjer] from comment #1) > This mockup is very interesting, but it seems to be focused on the > distribution of submissions per build and selection of builds rather than on > simple measurements. Did it get posted to the wrong bug? I think it should be possible to do this for every simple measurement
I actually have the same doubt as daniel. Where in the mockup is the simple measurement? You mean you're focusing on one simpleMeasure, then looking at the distribution of that simplemeasure through the app ids and then filter on those results?
(In reply to Pedro Alves from comment #3) > I actually have the same doubt as daniel. Where in the mockup is the simple > measurement? You mean you're focusing on one simpleMeasure, then looking at > the distribution of that simplemeasure through the app ids and then filter > on those results? Sorry, I screwed up my terminology. I think it would be nice to do this on .info and .simpleMeasurements. In this example i used appID. Once one filters on appID, distributions for .version, .appname, .OS, etc should update accordingly. One should then be able to filter on them as described. Sorry for the crappy mockup, I do not make my living from UI design.
I think that this mockup looks really interesting for showing the total number of submissions per build id. We can play with a way of using it to show simple measures too, but after a conversation with Luke, what I want to start with (if it is okay with you) is described in this project feature issue: https://metrics.mozilla.com/projects/browse/TM-10 Let me know what you think of that. You can comment in either place and I'll make sure it gets propagated. We are trying to use this project management system for new features and new project work and keep bugzilla for just actual bugs in existing deployments, but I don't want to hassle you with where you log stuff, that is on me to administrate.
This is just a proposed ui for displaying available data and filtering on it, I didn't mean to let this stop worked we agreed on earlier
grouping for triage
Status: NEW → ASSIGNED
Whiteboard: Telemetry -- needs PM project priority
Triaged.
Target Milestone: Unreviewed → Backlogged - BZ
Whiteboard: Telemetry -- needs PM project priority → [Telemetry:P1]
Whiteboard: [Telemetry:P1] → [JIRA BIV-110] [Telemetry:P1]
Target Milestone: Backlogged - BZ → Moved to JIRA
This bug is old, the main part that's missing is displaying the actual distribution of simple values. Filtering can be done in a subsequent bug.
Summary: Display distribution of simple values and allow filtering based on them → Display distribution of simple values
First approach on this is to develop a job that will query the raw data and build natural distributions of simple values. The output of these jobs will be used to guide the selection of buckets for the aggregation that appears in ES.
Is this still desired? I took over for Annie in September and I missed this entire bugzilla queue (my apologies!)....so I'm trying to figure out what's still useful and what is not, especially in light of the executive metrics dashboards.
No assignee, updating the status.
Status: ASSIGNED → NEW
No assignee, updating the status.
No assignee, updating the status.
No assignee, updating the status.
No assignee, updating the status.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: