Skip to main content

Proactive production support by trusting data

Five years ago when I joined my employer we were in reactive mode when it comes to production performance. Nodes were going down daily and we would jump to fix that fire and then move to next fire. Problem with this approach was that we would be always busy and even nightly calls for customers in Europe.  Similar pattern was happening when it came to production support, many issues were known only when a customer would report it. Again this would mean that we would get calls on weekend and we had to fix issues ASAP and sometimes that means putting a band-aid. Some times issues will linger in production unnoticed for 1-2 weeks and when customer would report it, its a lengthy and arcane process to hunt for issues in existing logs. More than debugging this would require  a lot of patience and persistence to look for trend and form a time-line of events to hunt for root cause. Only few engineers would be willing to do so.

Over the course of last few years we became better at production support by turning to proactive production support. I wrote a exception analysis report and  daily my team members and me would analyse exception report and send tickets to appropriate colleagues.  Many times there will be tickets that don’t require patch and can be temporarily fixed by doing some data cleanup. If the issue was in the flow executed by background jobs or automated agents then we would fix issues even before customer would notice it.  Advantage of this approach is that issues will get caught before it becomes a nightmare. Incremental fixes adds up to a lot and now the volume of production issues we have to fix has reduced because we fix many of them in the background and include it in coming patch.

Two months ago we installed new relic and we are not turning the table around on performance front also by trusting data rather than gut feelings.  New relic allows us to do trend analysis and release impact analysis, we can catch the issues while its turning from Green->Yellow->Red. Off course some issues turn from Green to Red within 10-15 mins but there are many that takes time. For e.g. Last week I noticed that one data centre is behaving odd and avg response time of all apis increased from 50ms to 100ms. That means customers were having degraded performance but still they were not complaining. Today I found it was due to one customer and the problem can be fixed by some data tweaks. I did the tweaks and performance is back to normal.

Similarly from new relic we found many issues where calls to memcached would happen in a loop or database queries in a loop. Those kind of issues affect customers with 25-30K users but not all customers. Every penny counts and by taking a proactive jab at these issues we are increasing customer satisfaction and loyalty but also we are becoming more predictable by trusting metrics.

for e.g. we recently converted a service from python to java and in past we have never ramped up from 0 to 1000 customers in a week.  But because of new relic I clearly saw that system was performing well with no errors even though we ramped from 30->200->1000 clients. Tomorrow we would add 500 more clients and all this is because the decision is based on data rather than gut feeling.



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
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(""); factory.setPort(5672); Conne…

Spring query timeout or transaction timeout

If you are using spring to manage transactions then you can specify default transaction timeout using

    <bean id="transactionManager"
        <property name="dataSource" ref="dataSource" />
        <property name="defaultTimeout" value="30" /> <!--30 sec--->             

or you can override the timeout in the annotation

    @Transactional(readOnly = false, timeout=30)

or if you are doing it programatic transactions then you can do

DataSourceTransactionManager transactionManager = new DataSourceTransactionManager(dataSource);

 or you can override the timeout for one particular transaction

TransactionTemplate transactionTemplate = new TransactionTemplate();

Python adding pid file

I have a thumbnail generator that launches multiple processes and the correct way to shut it down is to send kill -HUP to the parent process. To automate I had to write a pid file from python, it was a piece of cake
def writePidFile(): pid = str(os.getpid()) f = open('', 'w') f.write(pid) f.close()