Closed
Bug 1134182
Opened 11 years ago
Closed 9 years ago
get ship-it reporting to newrelic
Categories
(Release Engineering :: Applications: Shipit, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
References
Details
Attachments
(1 file)
|
1.26 KB,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
New Relic is awesome. Ship it could particularly benefit from it's ability to watch for and store information about errors and tracebacks.
Jake, Ship It is already running on the generic cluster. If I do https://github.com/mozilla/balrog/pull/20/files for it, should it Just Work?
Flags: needinfo?(nmaul)
| Reporter | ||
Comment 1•11 years ago
|
||
(In reply to Ben Hearsum [:bhearsum] from comment #0)
> New Relic is awesome. Ship it could particularly benefit from it's ability
> to watch for and store information about errors and tracebacks.
>
> Jake, Ship It is already running on the generic cluster. If I do
> https://github.com/mozilla/balrog/pull/20/files for it, should it Just Work?
Given that this works, I'm going to assume the answer is yes:
[bhearsum@generic1.webapp.phx1 ~]$ python
Python 2.6.6 (r266:84292, Nov 21 2013, 10:50:32)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-4)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import newrelic
>>>
We've got Chief set-up for this, so I can probably completely self serve this....
Flags: needinfo?(nmaul)
| Reporter | ||
Comment 2•11 years ago
|
||
Attachment #8566792 -
Flags: review?(rail)
Comment 3•11 years ago
|
||
Comment on attachment 8566792 [details] [diff] [review]
add newrelic support to ship it
Review of attachment 8566792 [details] [diff] [review]:
-----------------------------------------------------------------
Can you apply the comments below before you land? They are minor, but should make the code more readable.
::: kickoff.wsgi
@@ +8,5 @@
> + import newrelic.agent
> +except ImportError:
> + newrelic = False
> +if newrelic:
> + newrelic_ini = getenv('NEWRELIC_PYTHON_INI_FILE', False)
False is redundant here. Also having it as a boolean here is a bit weird. The default None is OK for this case.
@@ +12,5 @@
> + newrelic_ini = getenv('NEWRELIC_PYTHON_INI_FILE', False)
> + if newrelic_ini:
> + newrelic.agent.initialize(newrelic_ini)
> + else:
> + newrelic = False
I think the "else" block is redundant. Can you remove it?
Attachment #8566792 -
Flags: review?(rail) → review+
| Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 8566792 [details] [diff] [review]
add newrelic support to ship it
I landed this with the requested changes. I'll push it to prod sometime next week, when we're clear of releases.
Attachment #8566792 -
Flags: checked-in+
| Reporter | ||
Comment 5•11 years ago
|
||
I pushed this to prod today but it's not showing up in Newrelic. I'm guessing that something I don't have access to needs tweaking too.
| Reporter | ||
Comment 6•11 years ago
|
||
Mass component change for ship it bugs.
Component: Release Automation → Ship It
| Reporter | ||
Comment 8•11 years ago
|
||
Looks like we need WebOps to set something for us:
13:16 < bhearsum> did we ever figure out how to fix the generic "Python Application" issues that ship it and some other apps were hitting with new relic?
13:16 < Callek> bhearsum: if the wsgi or httpd environment set "newrelic.app_name" it fixes it
13:17 < Callek> bhearsum: basically I was told that if "you" had enabled new relic for ship-it without asking webops to set things up (like that environment var) this could happen
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Updated•4 years ago
|
Component: Applications: ShipIt (backend) → Applications: ShipIt
You need to log in
before you can comment on or make changes to this bug.
Description
•