[Django]-Web application monitoring best practices

Monitoring the number of connections to your Web server and your database is another good thing to track. Chances are if one shoots through the roof, something is starving for resources and the site is about to go down.

Also make sure you have a regular request for a URL that is a reasonable end-to-end test of the system. If your site supports search, then have nagios execute a search – that should make sure the search index is healthy, the Web server and the database server.

Also, make sure that your applications sends you email anytime your users see an error, or there is an unhandled exception. That way you know how the application is failing in the field.

If I had to pick one type of testing it would be to test the end-user functionality of the system. The important thing to consider is the user. While testing things like database availability, server up-time, etc, are all important, testing work-flows through your system via a remote UI testing system covers all these bases. If you know that the critical parts of your system are available to the end-user, then you know your system is prolly Ok.

1. Identify the important work-flows in your system. For example, if you wrote an eCommerce site you might identify a work-flow of “search for a product, put product in shopping cart, and purchase product”.
2. Prioritize the work-flows, and build out higher-priority tests first. You can always add additional tests after you roll out to production.
3. Build UI tests using one of the available UI testing frameworks. There are a number of free and commercial UI testing frameworks that can be run in an automated fashion. Build a core set of tests first that address critical work-flows.
4. Setup at least one remote location from which to run tests. You want to test every aspect of your system, which means testing it remotely. Is the internet connection up? Is the web server running? Is the connection to the database server working? Etc, etc. If you test remotely you make sure you system is available to the outside world which means it is most likely working end-to-end. You can also run these tests internally, but I think it is critical to run them externally.
5. Make sure your solution includes both reporting and notification. If one of your critical work-flow tests fails, you want someone to know about it to fix the problem ASAP. If a non-critical task fails, perhaps you only want reporting so that you can fix problems out-of-band.

This end-user testing should not eliminate monitoring of system in your data-center, but I want to reiterate that end-user testing is the most important type of testing you can do for a web application.

Ahhh, monitoring. How I love thee and your vibrations at 3am.

Essentially, you need a way to inspect the internal state of your application, both at a specific moment, as well as over spans of time (the latter is very important for detecting problems before they occur). Another way to think of it is as glorified unit-testing.

We have our own (very nice) monitoring system, so I can’t comment on Nagios or other apps. Our use case is similar to yours, though (cgi app on apache).

1. Add a logging.monitor() type method, which will log information to disk. This should support, at the least, logging simple numbers and dicts of numbers (the key=>value association can be incredibly handy).
2. Have a process that scrapes the monitoring logs and stores them into a database.
3. Have a process that takes the database information, checks them against rules, and sends out alerts. Keep in mind that somethings can be flaky. Just because you got a 404 once doesn’t mean the app it down.
4. Have a way to mute alerts (very useful for maintenance or to read your email).

Thats all pretty high level. The important thing is that you have a history of the state of the application over time. From this, you can then create rules (perhaps just raw sql queries you put into a config somewhere), that say “If the queries per second doubled, send a SlashDotted alert”, or “if 50% of responses are 404, send an alert”. It also bedazzles management because you can quantify any comment about whether its up, down, fast, or slow.

Things to monitor include (others probably mentioned these as well): http status, port accessible, http load, database load, open connection, query latency, server accessibility (ssh, ping), queries per second, number of worker processes, error percentage, error rate.

Simple end-to-end tests are also very handy, though they can be brittle. Its best to keep them simple, but you should have one that tries to touch core pieces of the app (caching, database, authentication).

I use Munin and Monit, and have been very happy with both of them.

Internal logging is fine and dandy but when your whole app goes down or your box/enviro crashes you need an outside check too. http://www.pingdom.com/ has been very reliable for me.

My only other advice is I wouldnt spent too much time on this. my best example is twitter, how much energy did they put into the system being able to half-die instead of just investing that time and energy into throwing more hardware / scaling it out.

Chances are what ends up taking you down, your logging and health systems will have missed anyway.

The single most important way to monitor any online site is to monitor externally. The goal should be to monitor your site in a way that most closely reflects how your users use the site. In 99% of cases, as soon as you know that your site is down externally, it’s relatively easy to find the root cause. The most important thing is to know as soon as possible that your customers are unable to load your site.

This generally means using an external performance monitoring service. They very from the very low end (mon.itor.us, pingdom) to the high end (Webmetrics, Gomez, Keynote). And as always, you get what you pay for. The things to look for when shopping around for a monitoring service include:

• The size and distribution of the monitoring network
• Whether or not the monitoring solution is able to monitor your site using a real browser (otherwise you aren’t testing your site like a real user would)
• The scripting language (to script the transactions against your site)
• The support department, to help you along the way, and provide expertise on how to monitor correctly

Good luck!

Web monitoring by IP Patrol or SiteSentry have been useful for us. The second is a bit like site confidence but slightly prettier lol.

Have you thought about monitoring the functionality as well? A script (either in a scripting language like Perl or Pyton or using some tool like WebTest) that talks to your application and does some important steps like logging in, making a purchase, etc is very nice to have.

Aside from what to monitor, which has already been answered, you need to make sure – whatever system you use – that you get only one notification of an error that happens multiple times, on each request. Or your inbox will run out of memory 🙂 Plus, it’s plain annoying…

Divide the standby shifts among the support/dev team, so one person does not have to be on call every single evening. That will wear people down. Monitoring is a good thing, but everyone needs to get a chance to have a life once in a while. Your cellphone buzzing at 2AM for a few nights will get very old pretty soon, trust me. And not every developer is used to 24/7 support, so you need to find the balance between using monitoring and abusing monitoring.

Basically, have distinct escalation levels, and if the sky is not falling, define a “serenity now” window at night where smaller escalation levels don’t go out.

I’ve been using Nagios + CruiseControl + Selenium for running high-level tests on mission critical web applications. I got burned pretty hard by a simple jquery error that stopped users from proceding through an online signup form.

http://www.agileatwork.com/the-holy-trinity-of-web-2-0-application-monitoring/

You can take a look at AlertGrid. This web application allows you to filter and forward alerts to your team (worldwide). It has also nice ability to monitor if something did not happen.

To paraphrase Richard Levasseur: ah, monitoring tools, how your imperfections frustrate me. There doesn’t seem to be a perfect tool out there; Nagios is pretty easy to set up but the UI is kinda old fashioned and you have to have a daemon running on each server being monitored. Zenoss has a much nicer UI including trend graphs of resource usage, but it uses SNMP so you have to have some familiarity with that to get it working properly, and the documentation is not the best – there are hundreds of pages but it’s really hard to find just the info you need to get started.

Friends of mine have also recommended Cacti and Hyperic, but I don’t have personal experience with those.

One last thing – one of the other answers suggested running a tool that stresses your site. I wouldn’t recommend doing that on your live site unless you have a reliable quiet period when nobody is hitting it; even then you might bring it down unexpectedly. Much better to have a staging server where you can run load tests before putting changes into production.

One of our clients uses Techout (www.techout.com) and is very pleased with the service.

There is no charge for alerts, no matter what kind or how many, and they offer email, voicemail and SMS alerts — and if something major happens, a phone call from a live person to help you out.

It’s all based on service — you don’t install the software and you have a consultant who works with you to determine the best approach for your business. It’s one of the most convenient web application monitoring services because they take care of everything.

I would just add that you can predict error likelihood somewhat based on history of past errors and having fixed them. With smaller scale internal testing if you were to graph the frequency and severity of problems that have been corrected to this point you’ll have an overview of predictable new problems. If everything has been running error free for some time now, then the two sources of trouble would be recent changes or scalability issues.

From the above it sounds like scalability is your only worry, but I just mention the past-error frequency test because the teams I’ve been on invariably think they got the last error fixed and there are no more. Until there is.

Changing the line a little bit, something I really think is useful and changed a lot how I monitor my apps is to log javascript exceptions somewhere. There’s a very nice implementation that logs that directly from user browsers to Google Analytics.
This is a must for Javascript centered web applications, and can give you results based directly on users browsers what can lead to very unexpected errors (iE and mobile browser are pain)

Disclaimer: My post bellow

http://www.directperformance.com.br/en/javascript-debug-simples-com-google-analytics

For the internet presence monitoring, I would suggest the service that I am working on: Sucuri NBIM (Network-based integrity monitor).

It does availability and integrity checks, looking for changes on your internet presence (sites, DNS, WHOIS, headers, etc) and loss of connectivity. It is free and you can try it out here.