Most IT teams have synthetic monitoring of their sites down. Now it's time to extend that vigilance to client-server applications.

Jasmine McTigue, Principal, McTigue Analytics

October 18, 2012

4 Min Read

InformationWeek Green - October 22, 2012

InformationWeek Green - October 22, 2012

InformationWeek Green

InformationWeek Green

Download the entire Oct. 22, 2012, issue of InformationWeek, distributed in an all-digital format as part of our Green Initiative
(Registration required.)
We will plant a tree for each of the first 5,000 downloads.

Application Early Warning System

Application Early Warning System

Ever feel like you're running blind, even with a costly and complex application performance monitoring system in place?

The problem is that APM mostly focuses on Web applications. But most IT teams are responsible for vital business applications that aren't Web based and that must be available pretty much 100% of the time--and by "available" we mean near-instant response, not taking 10 seconds to refresh a screen. Think about an inventory database that salespeople and partners depend on. It's extraordinary that many shops are still in the position of not knowing performance is tanking until the help desk lines light up. And if you can't proactively monitor mission-critical applications hosted in-house, you're going to be in worse shape if (or when) they start migrating to public cloud infrastructure services.

Most of the companies we work with have a good handle on how well their e-commerce applications and outward-facing websites are performing. Now the challenge is looking inward to head off problems with critical business applications before customers or employees notice.

The answer to doing that is using synthetic transaction monitoring for those in-house applications. While previously synthetic transactions were only for Web applications, leading APM providers, like those listed in our vendor comparison on p. 11, are starting to offer real transactional automation integration. The key word there is "starting." The information in our comparison is based on data provided by the vendors; we have not lab tested these systems, so caveat emptor.

Fundamentals: Application Early-Warning System

Our full report on application monitoring free with registration.

This report includes 15 pages of action-oriented analysis. What you'll find:

  • Preview of InformationWeek 2013 Virtualization Survey data

  • Discussion of the next step: analyzing network elements in real time with correlation

Get This And All Our Reports

We strongly suspect that most vendors are being, shall we say, overly optimistic in their assessments of their products' capabilities. Test in your infrastructure before assuming any APM system can support monitoring of internal applications.

What are we looking for? Instead of having to manually run a test transaction, you have a process do it for you at measured intervals. The system records the time to completion, perhaps even the time between different steps in the transaction. An operation suddenly takes 30 seconds instead of five seconds and that delay happens three times over a five-minute interval? You have a problem--and an email letting you know exactly what's up. Then, runbook or scripted automation sequences take a flagging application server, indicated by a transaction monitor, tear it down from the server farm, and add a clone to the pool. Now you can investigate without end users being inconvenienced. To do all that, you need to know it's down, and the application monitor will tell you in a better way than any other monitoring tool.

IT seems increasingly open to trying to achieve this level of automation. In our 2013 InformationWeek Virtualization Management Survey, which will be released in a few weeks, we delved into use of automation systems like Microsoft System Center, PuppetLabs, and Opscode Chef. While only 15% have this technology fully deployed, 40% are in the process. That's great news for IT and the business.

Of course, advanced automation builds on baseline key performance metrics, because once you know an application is malfunctioning, you need to know why.

To read the rest of the article,
Download the Oct. 22, 2012, issue of InformationWeek

Read more about:


About the Author(s)

Jasmine  McTigue

Principal, McTigue Analytics

Jasmine McTigue is principal and lead analyst of McTigue Analytics and an InformationWeek and Network Computing contributor, specializing in emergent technology, automation/orchestration, virtualization of the entire stack, and the conglomerate we call cloud. She also has experience in storage and programmatic integration.


Jasmine began writing computer programs in Basic on one of the first IBM PCs; by 14 she was building and selling PCs to family and friends while dreaming of becoming a professional hacker. After a stint as a small-business IT consultant, she moved into the ranks of enterprise IT, demonstrating a penchant for solving "impossible" problems in directory services, messaging, and systems integration. When virtualization changed the IT landscape, she embraced the technology as an obvious evolution of service delivery even before it attained mainstream status and has been on the cutting edge ever since. Her diverse experience includes system consolidation, ERP, integration, infrastructure, next-generation automation, and security and compliance initiatives in healthcare, public safety, municipal government, and the private sector.

Never Miss a Beat: Get a snapshot of the issues affecting the IT industry straight to your inbox.

You May Also Like

More Insights