Upgrade New Relic deployment to v2 API

RESOLVED FIXED

Status

Mozilla Developer Network
General
RESOLVED FIXED
5 months ago
3 months ago

People

(Reporter: jwhitlock, Unassigned)

Tracking

Details

(Whiteboard: [specification][type:bug])

(Reporter)

Description

5 months ago
What did you do?
================
Attempted to deploy Kuma, including telling New Relic that there is a deployment

What happened?
==============
An error occured:

http://developeradm.private.scl3.mozilla.com/chief/developer.stage/logs/2b5edeaca89a5b951113c70bd2ac58c2166627d1.1498586444

[2017-06-27 11:05:49] [localhost] running: curl --silent -H "x-api-key:df3bbd62e103c35dd67aae862eb686f3252568b7fe5d1d1" -d "deployment[app_name]=developer.allizom.org" -d "deployment[revision]=2b5edeaca89a5b951113c70bd2ac58c2166627d1
[localhost] running: " -d "deployment[user]=Chief" https://rpm.newrelic.com/deployments.xml
[2017-06-27 11:05:49] [localhost] failed: curl --silent -H "x-api-key:df3bbd62e103c35dd67aae862eb686f3252568b7fe5d1d1" -d "deployment[app_name]=developer.allizom.org" -d "deployment[revision]=2b5edeaca89a5b951113c70bd2ac58c2166627d1
[localhost] failed: " -d "deployment[user]=Chief" https://rpm.newrelic.com/deployments.xml (0.389s)

What should have happened?
==========================
The deployment should have registered w/ New Relic

Is there anything else we should know?
======================================
The application ID will need to be added to commander_settings.py so that it is accessible to chief_deploy.py

Comment 1

5 months ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/07c4a19b52a4eb8baa447c737c7c63ef30a6021a
bug 1376606: Disable New Relic v1 API call

https://github.com/mozilla/kuma/commit/fd59d019de1ea91d1ff8740fcfbc0675a4fe3421
Merge pull request #4295 from jwhitlock/disable-nr-1376606

bug 1376606: Disable New Relic v1 API call
(Reporter)

Comment 2

5 months ago
This Sentry issue may be relevant:

https://sentry.prod.mozaws.net/operations/mdn-stage/issues/617557/

There was also intermittent UI and API Availability on June 27th:

https://status.newrelic.com/incidents/bs8g1rkb0f2g

We can still use this as an opportunity to upgrade to the current v2 API.
(Reporter)

Comment 3

4 months ago
My current plan is to get the v2 NR API into the AWS deployment process, but to not upgrade the SCL3 deployment, since we plan to be out of SCL3 in the coming months.  Leaving open in case there is an easy opportunity to do this work.

Comment 4

3 months ago
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/4bc0730edf726fdd41e37809ea9a5a56fd60c773
bug 1376606: Update to New Relic v2 API

Update ping_newrelic to use the v2 API:
https://docs.newrelic.com/docs/apm/new-relic-apm/maintenance/recording-deployments

https://github.com/mozilla/kuma/commit/68e5fddfaaa3ef2488af60599ed3ea44afb13c60
Merge pull request #4358 from mozilla/deploy-1376606

bug 1376606: Update to New Relic v2 API
(Reporter)

Comment 5

3 months ago
I checked, and commander_settings.py does not appear to be a puppet-controlled file, so I had the access to add the application ID. I've tested on staging, will close after the next production push.
(Reporter)

Comment 6

3 months ago
Deployment recorded with production push.
Status: NEW → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.