Skip to main content

Kibana/logstash integration with reports or JIRA

We use Logstash for our centralized logging. All our app nodes track exceptions and write them to scribe, in night a python scribe consumer aggregates that information and sends an email with top exceptions with counts and first 200 characters of the exception.  Well the problem was that now I have to go through email and for each row I need to find the exception in logstash or in application logs. This is painful, I wanted to find some better way.


So I changed our exception tracking code to include a requestId into scribe logs and this requestId is logged with each exception to logstash. Now all I need to do is add a column in my table to include a logstash query link.  Problem is that it wasnt that straight forward. Ultimately after reading some forums I found that I need  to  prepare a search json and then base64 encode it and then create a url and voila I was done.  What used to take 1 hour to trace 10 exceptions would take me just 30 mins. 


    linkPrefix = "https://%s-logstash.xyz.com/#" % dc_name.lower()
    now_java_ts = int(time.time()) * 1000
    searchJson = """{"search":" @fields.requestid:\\"%s\\"","fields":[],"offset":0,"timeframe":"172800","graphmode":"count","time":{"user_interval":0},"stamp":%s,"mode":"","analyze_field":""}"""%(sampleRequestId, now_java_ts)
    searchJsonEncoded = base64.b64encode(searchJson)
    linkUrl = linkPrefix + searchJsonEncoded
    link = "
RequestId:%s" %(linkUrl, sampleRequestId)




The new report looks like



Other fancy things in the report are these Up and down arrows that tell me if the exceptions are going up or down and % will tell me how much they are up and down from yesterday or after a release.

the link on count will take me to graphite graph that tells me how an exception is trending and when it was introduced as shown below.



Comments

  1. UnknownJune 29, 2013 at 7:56 AM

    Ok - it took me a couple of reads to figure out what this is for, so correct me if I'm wrong...

    This is to add link into the emails you receive (or that JIRA receives) that allows you to navigate back into your logstash, at exactly the right point.

    The report you show is from JIRA.

    ReplyDelete
  2. Kalpesh PatelJune 29, 2013 at 10:37 AM

    Yes Martin, sorry if the blog post was cryptic, I am not a professional blogger and I wrote it in 5-10 min:).

    So yes we daily generate some reports from scribe logs and create JIRA tickets automatically. So I need the JIRA ticket and report to have a link to logstash so that the users can click on it to jump directly to logstash.

    ReplyDelete

Post a Comment

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 immediately
Post a Comment
Read more

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 can happe
Post a Comment
Read more

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 id="restoreJob" class="com.xxx.infrastructure.quar
7 comments
Read more