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

Haproxy and tomcat JSESSIONID

One of the biggest problems I have been trying to solve at our startup is to put our tomcat nodes in HA mode. Right now if a customer comes, he lands on to a node and remains there forever. This has two major issues: 1) We have to overprovision each node with ability to handle worse case capacity. 2) If two or three high profile customers lands on to same node then we need to move them manually. 3) We need to cut over new nodes and we already have over 100+ nodes.  Its a pain managing these nodes and I waste lot of my time in chasing node specific issues. I loath when I know I have to chase this env issue. I really hate human intervention as if it were up to me I would just automate thing and just enjoy the fruits of automation and spend quality time on major issues rather than mundane task,call me lazy but thats a good quality. So Finally now I am at a stage where I can put nodes behing HAProxy in QA env. today we were testing the HA config and first problem I immediat...

Adding Jitter to cache layer

Thundering herd is an issue common to webapp that rely on heavy caching where if lots of items expire at the same time due to a server restart or temporal event, then suddenly lots of calls will go to database at same time. This can even bring down the database in extreme cases. I wont go into much detail but the app need to do two things solve this issue. 1) Add consistent hashing to cache layer : This way when a memcache server is added/removed from the pool, entire cache is not invalidated.  We use memcahe from both python and Java layer and I still have to find a consistent caching solution that is portable across both languages. hash_ring and spymemcached both use different points for server so need to read/test more. 2) Add a jitter to cache or randomise the expiry time: We expire long term cache  records every 8 hours after that key was added and short term cache expiry is 2 hours. As our customers usually comes to work in morning and access the cloud file server it ...

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...