Home

Why Application Performance Management Matters Now

Comments | Charles Babcock, InformationWeek | January 09, 2013 10:36 AM


Today's average business application typically runs in a virtual machine, with several branches that go off the application server and out to a completely different application for a particular function or piece of data.

In some cases, that branching operation may not even be on premises. As cloud computing takes hold, the scenario of going out of the network to obtain what your application needs will become more commonplace, leading to more headaches for the struggling art of application performance monitoring.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

It's always been difficult to see what's going on inside the application. At the same time, doing so has become more crucial as applications become one of the main ways that customers interact with companies they wish to do business with.

The modern application performance management (APM) system requires an ability to see an application and its dependencies, compile statistics on normal operations, perform real-time analysis to detect anomalies, and do diagnostics to determine what can be done to correct what's gone wrong. No systems perform all functions perfectly, despite bringing some new strengths to the process.

One of the lesser-known APM systems, OpNet, in Bethesda, Md., has a product line that corresponds to several of these steps, including AppResponse Xpert for monitoring the end user experience, network and application; AppTransaction Xpert for "deep transaction performance analysis and prediction," according to its descriptor on the OpNet (now part of Riverbed) website; and AppMapper Xpert for mapping an application's parts and dependencies.

[InformationWeek's Art Wittmann argues APM suffers because vendors haven't kept up. See What's Killing APM?]

Covering the bases is one thing. Getting the end-user experience down cold, so that the IT administrator has an idea what the user is seeing as an application runs, remains a challenge. CA Technologies, with deep experience in dependent legacy systems, has also moved onto this ground with its own Internet monitoring from "77 points of presence," said Dave Cramer, CA's VP of product management.

Dummy transactions that mimic real ones can be launched from those 77 points of presence and response times monitored. If a customer is running an application in the cloud, CA's points of presence offer response times between that application and points of presence in 40 countries around the world. Cramer said CA is still building out its independent monitoring network and adds 6-7 more points per quarter.

The granddaddy of independent monitoring networks, however, is probably that of the largest pure-play application performance management vendor, Compuware. It springs from Compuware's Gomez acquisition and includes 150,000 points of presence in 168 countries. The computers at these points can launch dummy transactions and record response times, assembling a picture of cloud vendor, ISP and Internet performance that can tell a business much about what's going on with its application.

An ongoing problem, nevertheless, of seeing what the end user sees is caused by the frequent changes in browsers. Once dominated by Microsoft Explorer and Netscape Navigator, the field now includes Google Chrome and Mozilla Firefox, as well as Apple's Safari, open source Opera and several other entrants.

"Firefox and Chrome change multiple times a quarter. Application monitoring needs to recognize how browser displays differ. There's a cascading set of changes and drivers" that the application performance management system must keep up with, John Van Siclen, general manager of the APM business unit at Compuware. One of the advantages of implementing such a system is that it relieves the enterprise from tracking all the browser changes, he said. APM provides enough background intelligence "to survive this wave of complexity," at least in Compuware's case, said Van Siclen.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

COMMENTS

Tune In to BYTE
Facebook Twitter LinkedIn Newsletter RSS
Whitepapers
whitepaper
In this paper you will learn the five trends shaping the future of enterprise mobility. Learn how the rise of social media as a business application, the lurring between work and home, the emergence of new mobile devices, the demand for tech savvy employees and changing expectations of corporate IT will fundamentally change the workplace.
whitepaper
In a survey of more than 1,700 information workers (iWorkers) in North America, notebooks, desktops, and smartphones were found to be “must-have” devices, while tablets, slates, and netbooks were relegated to “nice-to-have” status, according to a commissioned study conducted by Forrester Consulting on behalf of Dell and Intel.
Sponsored by: Dell
Upcoming Events