Top Five Monitoring Excuses (and why they don’t matter)

You’ve heard it all before. You’ve sat through the meetings. You’ve seen the finger pointing and you might even have played the blame game yourself once in a while. There’s always someone else to blame for your performance problem — whatever it is.

The fact is monitoring software can solve some of the problems your company faces as it deploys a web site or application but it’s not always a simple matter to track down the nature of a problem when there are so many variables involved. We all get that, but lets have some fun, step back for a moment and take a look a the top five monitoring excuses.

Something went wrong and these old chestnuts always seem to work.

The Business Unit Doesn’t Get It
This one always works great. When one of the business unit is having problems with an application or internal web site, blame them for not understanding how it works. It’s the classic blame the victim ploy and it’s used every day inside organizations. If they don’t get how the thing works, it must be their ignorance, right?

It’s The Developer’s Problem
When you can’t blame the victim, blame the developers. After all, they were the ones who created your application or website and if it’s not working the way it should or there are performance complaints, it has to be a configuration or a design problem on the developer’s end. Everything checks out, so what else can it be?

It must be an end-user configuration issue
This is related to the business unit excuse, but in this one, the users might understand the application, but the performance issue is due to a hardware configuration on their end, which is completely out of your control. Why should you be accountable for bad hardware?

It’s an External Problem Beyond Our Control
The beauty of this excuse is that it covers just about any situation. You know there’s a problem, but you can’t identify it using any of your tools, so therefore, it’s not your problem. ┬áThere are always a myriad of possible answers to any performance problem, so if it’s not in your control, how can you be expected to fix it?

While it’s fun to collect common excuses for performance issues, and these all have a hint of truth to them, the fact is if you’re reading this blog, you’re probably in the performance monitoring business and you want to track the source of your problem because it what’s you do.

So throw away those excuses and go forth and use the skills and tools at your disposal to fix the issue and let those excuses be damned.

What’s the best excuse you’ve heard? Leave a comment and let us know.

No Comments


  1. Tracking the Tough Problems | Real User Monitoring - [...] who simply don’t understand or bad programming or a database malfunction or something. (See Top Five Monitoring Excuses, for…

Leave a Reply

Your email address will not be published. Required fields are marked *