If you're new here, you may want to subscribe to my RSS feed. Not sure how to subscribe to a RSS feed? Read Subscribing to blogs the easy way. Thanks for visiting!
Our internet presence has been slow of late. Customers were complaining that the website was slow, we couldn’t log into the server reliably, sending emails was slow. All told not very good.
I remembered a while ago getting a call from my hosting rep saying that our bandwidth was maxed out. Many hosting providers provide unlimited bandwidth but limit the size of the pipe to your server. This has the benefit that whatever happens you know how big your hosting bill is going to be. The downside is that when the usage approaches the pipe limit, some traffic will start to slow down or fail. And there won’t be any discrimination between important money earning traffic and none monetised traffic.
One of the things I discovered, and corrected quickly, was the lack of any stats for our main download website. The log was sitting there but no usable stats were being drawn from it. I knew from the other websites we run that we were missing 35 GB of traffic this month. It turns out that the download site was the culprit.
One interesting side effect was that we discovered that back in May 325.63 GB was used by the download site. My suspicion is that our hosting provider might have said that they were limiting the size of our pipe but they weren’t in reality. If they had been, our server would have been completely unusable in May.
Anyway, the side effect of all of the above is that we are pulling our distros of a number of open source tools. The world of open source is a very different place than when we started back in 2003. Projects have gotten a lot better at packaging themselves on Microsoft Windows. We will be concentrating our efforts upon creating a set of network management tools for Windows PowerShell instead.
The main lesson I take away from this is to make sure you’re creating meaningful stats for everything you’ve got because you never know what may be causing you a problem. Just logging stuff isn’t anywhere near enough, a two gigabit log file won’t yield its secrets very easily.
Popularity: 11% [?]
Related posts:
{ 1 trackback }
{ 2 comments… read them below or add one }
Literally yesterday, I found out that a process was being run nightly for a client that we don’t have any more. Since this one client didn’t have any data in our systems, it was freaking out our programs and producing 100GB of logs a month…yes, *100GB* per month. Even with logrotated running, the compressed logs were insane. I thought that it was a valid process that was just logging too much, and the client services manager mentioned that they weren’t our client any more, a light dinged in my head and I said “lets put a stop to this!”
@Matt – that’s a lot of log to read through