1120492 - Add New Relic to geo.mozilla.org

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task)

Description

[Osmose [:osmose, :mkelly]]

We added the code for supporting New Relic to geo.mozilla.org in bug 860495. It looks for the newrelic.ini file specified by the NEW_RELIC_CONFIG_FILE environment variable and the license key in the NEW_RELIC_LICENSE_KEY environment variable.

Can we install the New Relic python library on the geo.mozilla.org servers and configure it to send data to our New Relic instance?

Comment 1

[Osmose [:osmose, :mkelly]]

This will also require pulling the latest geodude code, and I'd like to try that on a staging environment first as the marketplace folks have made some changes for their instance that might require some changes to our instance as well. I forget; do we have a staging environment for geodude already?

Comment 2

[Giorgos Logiotatidis [:giorgos]]

Also NEW_RELIC_APP_NAME environment variable is required for application name.

NEW_RELIC_APP_NAME and NEW_RELIC_LICENSE_KEY are required env variables. NEW_RELIC_CONFIG_FILE can be skipped and the included newrelic.ini will be used.

Comment 3

[C. Liang [:cyliang]]

I've installed the NewRelic python agent on the geo.mozilla.org dev server and added the usual environment variable to the Apache configuration file to set the NewRelicapplication name.  However, even after restarting both the New Relic processes and Apache, it doesn't look like the python agent is being invoked by the app.

I'm wondering if your need to tweak the WSGI to pick up the NEWRELIC_PYTHON_INI file rather than the NEWRELIC_INI file.  Looking at some of the other applications that are reporting correctly, the invocation looks something like:

try:
    import newrelic.agent
except ImportError:
    newrelic = False

if newrelic:
    newrelic_ini = os.getenv('NEWRELIC_PYTHON_INI_FILE', False)
    if newrelic_ini:
        newrelic.agent.initialize(newrelic_ini)
    else:
        newrelic = False

I believe that the default ini file that is created by puppet (python.ini) already has the  NewRelic license key embedded in it.


[1] SetEnv newrelic.app_name geo-dev.allizom.org

Comment 4

[Giorgos Logiotatidis [:giorgos]]

I pull requested with the changes suggested in #3. Once this is merged we can try again.

https://github.com/mozilla/geodude/pull/8

Comment 5

[Giorgos Logiotatidis [:giorgos]]

OK :cyliang can you pull the latest code and try again? We are reading NEWRELIC_PYTHON_INI_FILE env variable now. 

Thanks!

Comment 6

[C. Liang [:cyliang]]

After some monkeying with dependencies, I believe the app is now reporting to New Relic:

   https://rpm.newrelic.com/accounts/263620/applications/5842665

There's not much data but, then again, it looks like there aren't many requests sent to this server.   I don't know if more code changes need to happen before additional data will show up -or- if more data will show up if there's more traffic sent to the dev environment.

Comment 7

[Giorgos Logiotatidis [:giorgos]]

I triggered some traffic to geo-dev.a.o and it NewRelic works as expected. Please proceed with prod deployemnt

Comment 8

[C. Liang [:cyliang]]

I installed the new NewRelic packages in stage and pulled the code changes from git.  Data is now being reported to NewRelic for geo.mozilla.org:  
    https://rpm.newrelic.com/accounts/263620/applications/5867030