Closed Bug 627568 Opened 13 years ago Closed 13 years ago

Add Input data into elastic search

Categories

(Input Graveyard :: Search, enhancement, P1)

enhancement

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: aakashd, Assigned: davedash)

References

Details

(Whiteboard: [launch-steps] [qa-])

It'd be great to let the Mozilla community create some great visualizations (mix in some ADU's, searches, modifiers, etc.) and dashboards out of our database...just not on the Input dashboard. Let's use this bug to catalog ideas and implementation.
Reason #2: It'd be nice to be cool like the rest of the web and have one too.
APIs are good, but they're hard to do right, especially for open-ended questions.  If there are ways to do so without leaking PII, figuring out ways to grant access to the raw data could be a bootstrapping step to give insight into what kinds of APIs cowpaths to pave.  Of course we're talking about a lot of data, so _access_ to the data is likely more practical than distributing the data to the world.

Someone pointed me to disco (http://discoproject.org/) which sounds like it could be a fairly generic way of doing so using fairly common tools within Mozilla.  I'm sure there are other options, but I figured I'd mention it.
Blocks: 627573
This does not block bug 627573, removing. Pulse integration doesn't need an API, unless we were going to scrape it via polling and synthesize Pulse messages...which defeats the whole point of Pulse.
No longer blocks: 627573
Of course I should mention that most tools leverage an API for an initial data load and then use Pulse for streaming live data/changes...so an API is useful though not necessary for Pulse integration
Here's a rundown of what people from specific teams would like to do with an api:

Metrics
-> get a spike in feedback no matter if its positive or negative
-> ask for a cluster ID and work with the messages within them to determine other metrics like sentiment

Support
-> correlate spikes in pre-defined terms in Input with matching summaries of SUMO threads
-> match clustered themes to support threads
-> get a spike in feedback for issues into bugzilla

RRRT
-> Look for comments and URLs in bugs and compare them to messages on Input
-> Look for comments and URLs in crash signatures on crash-stats and compare them to messages Input
-> Build an extension like the blocker-reports extension to post latest graphs and general happy/sad data across the user's own modifiers (i.e. platform, locale)
Target Milestone: --- → 3.4
Target Milestone: 3.4 → 4.0
Priority: -- → P1
L10n: create dashboards that show input counts for a set of locales.

i.e. counts of total, plus, negative, for a set of locale codes. Probably for an optional time range.
Assignee: nobody → dd
Changing the title to lock down the scope.  All these consumers are internal, so the best approach will be to add this data to elastic search, which will be internally available.

The data will likely be in a ES collection named 'input' in the public metrics cluster.
Summary: Need an API to let people do creative things → Add Input data into elastic search
Assignee: dd → nobody
Component: Input → Search
Product: Webtools → Input
QA Contact: input → search
Version: Trunk → unspecified
Moving to 4.1.
Assignee: nobody → dd
Target Milestone: 4.0 → 4.1
Bump to 4.2
Target Milestone: 4.1 → 4.2
Dave, this has missed for two releases; why has it been bumped to 4.2? If it's not going to land for 4.2, it'd be great to know how much work is still left to finish here as other teams are waiting on the work in this bug to deliver solutions themselves.
4.1 code freezed yesterday and this wasn't done by freeze.
Done.

http://github.com/fwenzel/reporter/commit/1214449


Dependency made because we can't verify it .. yet.
Status: NEW → RESOLVED
Closed: 13 years ago
Depends on: 664308
Resolution: --- → FIXED
Whiteboard: [launch-steps] → [launch-steps] [qa-]
Verified as [qa-]
Status: RESOLVED → VERIFIED
Product: Input → Input Graveyard
You need to log in before you can comment on or make changes to this bug.