Closed
Bug 1200379
Opened 9 years ago
Closed 7 years ago
Annotate New Relic transactions with Papertrail log search URLs
Categories
(Tree Management :: Treeherder: Infrastructure, defect, P3)
Tree Management
Treeherder: Infrastructure
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: emorley, Unassigned)
References
Details
We'll only really be able to do this once we move to Heroku (since current stage/prod aren't reporting there), but this looks pretty handy: http://help.papertrailapp.com/kb/integrations/new-relic/
Reporter | ||
Comment 1•9 years ago
|
||
Also: https://devcenter.heroku.com/articles/http-request-id#usage-with-django
Reporter | ||
Updated•8 years ago
|
Blocks: treeherder-heroku-polish
Reporter | ||
Updated•8 years ago
|
Priority: P4 → P3
Comment 2•8 years ago
|
||
:emorley In case you're interested, I've implemented that for ATMO here: https://github.com/mozilla/telemetry-analysis-service/blob/4f25b90c825769fe82c7b517d5869f05bb42ae8c/atmo/utils/middleware.py
Reporter | ||
Comment 4•7 years ago
|
||
Thinking about this more, we don't really have many cases where cross-referencing between a New Relic event and Papertrial is useful. Either there is an exception in New Relic which has all the details, or else there is nothing in New Relic and some convoluted log output in Papertrial (eg out of memory, dyno being killed messages). As such, let's not worry about this for now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Reporter | ||
Updated•7 years ago
|
Assignee: emorley → nobody
You need to log in
before you can comment on or make changes to this bug.
Description
•