Skip to main content

New relic and statuspage.io integration

Monitoring tools exposes a lot of data and we use Nagios, cacti, graphite,newrelic, mixpanel, flurry, boundary and many more tools.  But one of the ask for Support and marketing teams is how can they internally know if something is wrong. We cant expect them to wade through so many systems and so many applications to make sense of what is operational and what is not.  For e.g. we use a lot of services to serve the cloud filer server solution and this is the first page of status of our services in new relic and it spans 2 pages.

Support team and management relies on Operations team to notify them if an issue is on going. To make this easy I did a Proof of concept integration application responsible for serving main website with Statuspage.io.  The idea is simple

  1. Create public metrics in statuspage.io that are human readable.
  2. Query new relic and various systems for application status.
  3. Map new relic green/red/yellow status and other system status to statuspage.io status.
  4. If there is a status change then update statuspage.io metric status.
  5. Statuspage.io lets user subscribe to status change via SMS or email so support can  signup for that.
  6. Once this is fully baked then we can make this public and let customers do the same.
 

Now this is a proof of concept so I wrote a python script only with new relic integration with one application. I setup a cron job that runs every 2 min to do this integration. But we can enhance this script to derive status from various tools like new relic/nagios/boundary and map it transitively to human readable status. We can then even load this page up in various Tv screens in all offices to improve visibility.

The script I used to do the integration was for proof of concept and I cooked up in 2-3 hours including api research so use with caution.

import os
import sys
import requests
import logging
from logging.handlers import RotatingFileHandler

spiPageId = "PutYourPageIdHere"
cloudComponents = ["Metadata APIs","Web Interface","Webdav","Sharing"]
nrToSpiStatusMap = {"green":"operational", "yellow":"degraded_performance", "red":"major_outage"}

def getNewRelicApplications(apiKey):   
    interestedApps = ["cloud","mobile"]
    status = {}
    url ="https://api.newrelic.com/v2/applications.json"
    headers = {'X-Api-Key': apiKey}
    logging.info(url)
    r = requests.get(url, headers=headers)
    json=r.json()
    for application in json["applications"]:
        if application["name"] in interestedApps :
            status[application["name"]] = application["health_status"]
    return status

def getSpiComponents(spiApiKey):
    url ="https://api.statuspage.io/v1/pages/%s/components.json" % spiPageId
    headers = {'Authorization:': "OAuth %s" % spiApiKey}
    logging.info(url)
    r = requests.get(url, headers=headers)
    json=r.json()
    return json

def updateSpiComponent(spiApiKey, componentId, status):    
    url ="https://api.statuspage.io/v1/pages/%s/components/%s.json" % (spiPageId, componentId)
    headers = {'Authorization:': "OAuth %s" % spiApiKey}
    data = {"component[status]":status}
    logging.info(url)
    r = requests.patch(url, data=data, headers=headers)
    json=r.json()
    return json
   
def deriveSpiComponentToUpdate(spiApiKey, newRelicAppStatus):   
    spiComponents = getSpiComponents(spiApiKey)
    nrCloudStatus = newRelicAppStatus["cloud"]
    spiCloudStatus =  nrToSpiStatusMap[nrCloudStatus]
    componentsToUpdate = {}
    for component in spiComponents:
        if component["name"] in cloudComponents :            
            if component["status"] != spiCloudStatus :
                componentsToUpdate[component["id"]] = spiCloudStatus
    return componentsToUpdate

def updateSpiComponents(spiApiKey, componentsToUpdate):   
    for componentId in componentsToUpdate :
        status = componentsToUpdate[componentId]
        updateSpiComponent(spiApiKey, componentId, status)
            
def init():
    logger = logging.getLogger('')
    logger.setLevel(logging.DEBUG)

    log_format = 'Process-%(process)d %(asctime)s %(levelname)-8s %(message)s'
    handler = RotatingFileHandler("statuspage.log", maxBytes= 20 *1024 * 1024 , backupCount=10)   
    handler.setFormatter(logging.Formatter(log_format))
    logger.addHandler(handler)
   
# Main
if __name__ == "__main__":
    newRelicApiKey = sys.argv[1]
    spiApiKey = sys.argv[2]
    init()
    newRelicAppStatus = getNewRelicApplications(newRelicApiKey)
    componentsToUpdate = deriveSpiComponentToUpdate(spiApiKey, newRelicAppStatus)
    updateSpiComponents(spiApiKey, componentsToUpdate)    


Comments

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.
import org.slf4j.Logger;import org.slf4j.LoggerFactory; import java.io.OutputStreamWriter; import java.io.Writer; import java.net.Socket; import java.util.HashMap; import java.util.Map; public class GraphiteLogger { private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class); private String graphiteHost; private int graphitePort; public String getGraphiteHost() { return graphiteHost; } public void setGraphite…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…