RPM Status

New Relic RPM offers integration with 37signals’ Campfire product, so you can be notified of application deployments and incidents automatically in a Campfire chatroom.  When 37signals switched over to a new authentication system for their products on December 14, our Campfire integration broke.  We apologize for the inconvenience this has caused you.

The good news is 1) we have it working again and 2) we now authenticate using your Campfire authentication token.

To re-enable Campfire notifications with RPM, we need your new token.  Follow these steps to get Campfire back:

1. If you haven’t already, create your 37signals ID (https://37signals.com/accounts)
2. Log in to your Campfire account with a web browser.  Click the “My info” link and copy the “API authentication token”, a long alphanumeric string.
   
3. Log in to RPM and go to your Account Settings.  Click the Integrations tab, then the Campfire tab on the left.
   
4. Enter the authentication token in the form field and click Connect.  If the token matches, you’ll see a list of chat rooms appear.  Make a selection and click Save.  You’re good to go!
   

If you have any problems, please drop us an email at support@newrelic.com.  Thanks for being our customer!

Starting at around 9pm last night, a small subset of our customers have been experiencing gaps in their data. We’ve determined that this is entirely a user interface problem: your applications are correctly reporting data to us and we are correctly storing it, but we are not correctly retrieving it for display. We expect the data to be displaying again within a half hour.

Sorry about that.

We are doing some mysql upgrades  9:45 PM Pacific. Some customers will be unable to access their data for a short time.

Sorry for any inconvenience,

The New Relic Team

At about 12:20 we had a server panic during a routine disk replacement.
It took a few minutes for the system to come back up and a little while to verify that there was no corruption in MYSQL.
We maintain a replica of that database but we decided not to fail over as we were pretty certain it would take less time to bring the server back online than it would to fail over.
We generally hang the maintenance page during outages. Our maintenance page has a link to our status blog.  We could not do so because some UI slices were down and our deployment tool was not responsive quickly enough.

Remediation:
It is an unfortunate fact of life that hardware will fail every so often however we will continue to try to improve our systems and reliability.
We also need to work out a way for our deployment tools to be more resilient in the event of a slice failure. The maintenance page is an important tool we use to keep our customers informed about what is going on with RPM and we will work to insure it gets deployed in a timely way in the event of a problem.

We apologize for any inconvenience.

The New Relic Team

We will be performing a short maintenance around 9 PM PDT. Some customers will be unable to access RPM at this time.