Closed
Bug 1151800
Opened 10 years ago
Closed 9 years ago
Send Heroku logs to the Mozilla papertrail account
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P2)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: mdoglio)
References
Details
Breaking out of the overall Heroku bug (bug 1145606), since this is one of my deliverables for this quarter:
https://docs.google.com/a/mozilla.com/document/d/1U3VXk7K5iTmZvqqtX4sc-Znhch9ZAD98Vl1OyWRqZwo/edit#
Reporter | ||
Updated•10 years ago
|
Summary: Investigate log aggregation and Heroku, possibly using Papertrail → Investigate log aggregation with Heroku, possibly using Papertrail
Assignee | ||
Comment 2•9 years ago
|
||
I setup papertrail on https://treeherder-heroku.herokuapp.com/, you can access it via the heroku dashboard. For the next ten days we have a 1GB limit for free. After that keeping the same limit will cost 125$/month. The current log level for celery and gunicorn (INFO) is probably too verbose. We may want to switch to WARNING or even ERROR to limit the size of the logs.
Reporter | ||
Comment 3•9 years ago
|
||
Great :-)
Yeah I was planning on tweaking the log output - papertrail also offers filters that you can use on top, which don't count against your usage.
Assignee | ||
Comment 4•9 years ago
|
||
Shall we mark this done?
Reporter | ||
Comment 5•9 years ago
|
||
Yeah, the current log volume seems fine (it's much much less than what taskcluster is outputting), so I don't think we need to tweak it.
Assignee: emorley → mdoglio
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Summary: Investigate log aggregation with Heroku, possibly using Papertrail → Send Heroku logs to the Mozilla papertrail account
You need to log in
before you can comment on or make changes to this bug.
Description
•