Closed Bug 1032236 Opened 10 years ago Closed 10 years ago

Upgrade New Relic client on MDN servers

Categories

(Infrastructure & Operations Graveyard :: WebOps: Community Platform, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jezdez, Assigned: cliang)

Details

(Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/459] )

New Relic offers tracking AJAX requests if we upgrade to the latest version of their agent (newrelic>=2.10.1.9). The latest version is 2.22.0.19 according to https://docs.newrelic.com/docs/releases/python https://www.dropbox.com/s/nimpz4l4ikupnxg/Screenshot%202014-06-30%2015.46.15.png We're currently investigating frontend rendering performance issues and that would help a lot.
Whiteboard: [kanban:https://kanbanize.com/ctrl_board/4/459]
Assignee: server-ops-webops → cliang
@jezdez: I've updated the python agent to 2.22.0.20 on both the dev and staging environments. Can you tell me if this upgrade gives you the ability to track AJAX requests before I upgrade the production servers? This ended up requiring more work than originally planned for because of some file permissions changes that happened with newer version of the client. For future reference by webops folks, see the caveats I've added to https://mana.mozilla.org/wiki/display/SYSADMIN/Creating+NewRelic+RPMs.
Flags: needinfo?(jezdez)
Flags: needinfo?(jezdez)
Updated production webheads with the new NR python agent and data is appearing at https://rpm.newrelic.com/accounts/263620/browser/3172075/ajax_requests
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in before you can comment on or make changes to this bug.