[socorro-crashstats] implement CSV output

RESOLVED FIXED

Status

Socorro
Webapp
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: rhelmer, Assigned: peterbe)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: https://github.com/mozilla/socorro-crashstats/issues/50)

(Reporter)

Description

5 years ago
Used by:

topcrashers ( e.g. https://crash-stats.mozilla.com/topcrasher/byversion/Firefox/16.0a1/7?format=csv )

crashes per user ( e.g. https://crash-stats.mozilla.com/daily?p=Firefox&v[]=16.0a1&throttle[]=100&os[]=Windows&os[]=Mac&os[]=Linux&date_start=2012-06-25&date_end=2012-07-09&form_selection=by_version&csv=1&hang_type=any )
(Reporter)

Comment 1

5 years ago
Our needs are probably simple enough for this:

https://docs.djangoproject.com/en/dev/howto/outputting-csv/
(Reporter)

Comment 2

5 years ago
There is some work done on this:
https://github.com/mozilla/socorro-crashstats/pull/57
(Assignee)

Updated

5 years ago
Depends on: 788043
(Assignee)

Comment 3

5 years ago
Partial PR for the topcrashers
https://github.com/mozilla/socorro-crashstats/pull/100
Peter,

If we run into performance issues, Postgres can also generate CSV from a query. The reason I bring this up is that the Django CSV stuff is, in my experience, very slow and CPU-intensive.  Try the Django way first, of course.
(Reporter)

Comment 5

5 years ago
(In reply to [:jberkus] Josh Berkus from comment #4)
> Peter,
> 
> If we run into performance issues, Postgres can also generate CSV from a
> query. The reason I bring this up is that the Django CSV stuff is, in my
> experience, very slow and CPU-intensive.  Try the Django way first, of
> course.

Good point, however our django UI does not talk to postgres (except for session), it would be the middleware doing this.

Currently the middleware does a query and returns JSON, and the views implemented in Django decide whether to render that to HTML, CSV, RSS, etc.
(Reporter)

Comment 6

5 years ago
(In reply to Peter Bengtsson [:peterbe] from comment #3)
> Partial PR for the topcrashers
> https://github.com/mozilla/socorro-crashstats/pull/100

Why is the PR closed?
(Assignee)

Comment 7

5 years ago
(In reply to Robert Helmer [:rhelmer] from comment #6)
> (In reply to Peter Bengtsson [:peterbe] from comment #3)
> > Partial PR for the topcrashers
> > https://github.com/mozilla/socorro-crashstats/pull/100
> 
> Why is the PR closed?

That's a "bug" in github. There is a reference to another PR in there which is closed. The #100 is still open.
(Assignee)

Comment 8

5 years ago
The CSV output for Top Crashers has landed
https://github.com/mozilla/socorro-crashstats/commit/fea4b783b148c3f86137a5914419ea5280e2d586

Now Just waiting for the Top Crashers By User report to do the second part.
(Assignee)

Comment 9

5 years ago
PR for the daily report: 
https://github.com/mozilla/socorro-crashstats/pull/155

Comment 10

5 years ago
Commit pushed to master at https://github.com/mozilla/socorro-crashstats

https://github.com/mozilla/socorro-crashstats/commit/821cebc048bff72b9417cfa148e40ba1b3c103a0
bug 788055 - csv format output on the /daily report, r=rhelmer
(Assignee)

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.