-->

Sunday, July 31, 2016

Website Availaibility with New Relic

NewRelic is a great tool to monitor the webapplications , see the insights of the various transactions occurring in the applications and track the code issues. It helps you identify the response times from the different geographical locations and helps you optimize the user experience by  reducing the load times for your applications.

If you just want to monitor the website availability you can use the ping monitor of the newrelic. Its simple and don't require any agents configuration upfront and the advantage is that though the traditional monitors monitor for the website http status i.e. 200 for the site loading but won't check if the content is actually loaded or not. This can sometimes cause an issue, while newrelic gives you a functionality where you can monitor the string on the page load and if the newrelic doesn't find that string it would raise an alarm.

You can configure the ping for a website as follows, in our example we have simply put the monitor for the google website you can replace it with your own.



Start by logging in to your newrelic account.

You would get 4 options to choose from select the ping over there.

Enter the name of your monitor , the name should be choosen such a way that you would easily recognize what the monitor is for. Than enter the URL of your webapplication which you want to monitor and name of the string which loads on that webpage to make sure the content is loading up.

Next you can select the monitoring locations , the advantage of this is you can select the load times of these locations and see how your application is responding at different places.




You need to select the monitor frequency, like how much time you want the next check to happen.

Next you need to enter the email id on which the alerts would be sent. This can be your email id or your teams Dl.

Once done click on create my monitor to create the monitoring.


You should be able to see the monitor in your newrelic dashboard now, click on it to see the details.



If you will click on the monitor you would see the load time graph for  your monitor which shows the load time plotted on a graph so if your site becomes unavailable it would be shown on the graph.


The newrelic shows you the slowest results you can click on it to check it further.


You would see the site is having a redirect which is taking the time to load , you can see the similar information for  your application if any third party api is responding slow causing slowness on your webapplication.

If you will click on the redirect you would further be able to see whats taking the maximum time. like loading of webapplication comprises of DNS, Connect, SSL. Send , wait ,receive and time of first byte , you can see time for these over in the dashboard.


There is an option of downloading HAR. If  you will click on it , it would eventually download all the content in the json format which you could use to further process or built your own logic based on it.


If you will click on the results in the left most column, Than it would show you the load time for the Blocking, DNS lookup , SSL Negotiation, Connecting, Sending , waiting , Receiving.


You can click on failures to see if anything is failing on your web-application.


Next is your SLA , if you click on it Than you would be able to see the Apdex score  for your webapplication , the score closer to 1 means your user is quite satisfied with your site load time , a lower score means your site is slow and  you might loose them because they won't wait for your site to load and might think its hang or not working and move on.


You can generate the weekly and monthly reports on the SLA and can use it further improve your applications availability and response.

Next is your General , now if you want to make any changes to your earlier configuration , you can do it from here.



Last  one is your alert notifications and you can add the multiple email ids here for the alert like your infrastructure team , development team, devops teams etc.


0 comments:

Post a Comment