Tuesday, April 19, 2005

Wily Technology Releases Browser Response Time Adapter

Wily continues to lead the market for J2EE Applications Performance Management by doing things the right way. A critical element of any APM solution is the measurement of actual end user experience. For J2EE applications which have a web server as the front end, one right way to measure end user experience is to measure how long the application system takes to respond to each user request. Since each user request comes in the form of a URL, measuring the arrival time of that URL and then the gap to the response on the part of the application system to that URL is one of the "right" way to do things. Of course, Wily does not stop at the measurement of just the response time, since the IntroScope product can then drill into the middle tier components on J2EE applications servers to find out why response time has degraded.

Wily is also correct in its approach of not relying upon synthetic transactions (scripted agents emulating real users). APM Experts believes that while a script may be useful during QA, and it might be useful as a beginning of the day check (to see if the system is working before real users log on), there is no way that scripts can be written to accurately emulate what real users do. It is also extremely difficult to use scripted synthetic agents to emulate the combination of actions that a set of production users take on a live application system. Please see the article "Why are Scripts and Synthetic Transactions Undesirable" in the Analysis section of the APM Experts web site for more details on this subject.

Bernd Harzog
CEO
APM Experts
bernd.harzog@ampexperts.com

Friday, April 15, 2005

Who will Grab the Brass Ring in Application Management?


Here is an interesting disparity for you to think about. If you have invested a reasonable amount in network and systems management tools, your IT department should be able to:

  1. Keep your servers and networks up and running
  2. Monitor on an ongoing basis how utilized they are
  3. Use change management software and processes to manage keeping them up to date
  4. Use capacity planning tools to understand when to upgrade them
  5. Commit to service levels in terms of the availability and capacity of these resources

On the other hand, you are highly unlikely to have an analogous set of capabilities for your applications. For example, you probably:

  1. Cannot keep your applications up and running as smoothly as your servers and networks
  2. Cannot know on an ongoing basis how utilized an application is relative to its capacity to support users and work
  3. Do not know what the performance (response time) the application is delivering to each of your end users
  4. Cannot quickly and effectively identify problems in the applications, resolve them, and get the changes into production
  5. Cannot commit to application service levels that credibly promise availability and performance levels of the applications to your users.

There are three groups of vendors who collectively stand some chance of addressing this set of issues:

  1. Traditional infrastructure monitoring vendors (BMC, CA, IBM/Tivoli, NetIQ, HP, etc.). While these vendors products are very widely installed in enterprise IT shops they have neither a robust ability to measure applications availability and performance, nor any ability to assist in the application problem resolution process. These vendors are therefore the least likely of the three groups to be the source of a meaningful solution to the problem.
  2. APM focused monitoring vendors (Wily, Veritas, Mercury, Compuware, Quest, VIEO, ProactiveNet, eG Innovations, Premitech, etc.). These vendors all focus heavily upon measuring applications performance (response time), and offer in some cases (J2EE) a reasonable ability to pinpoint problems in middle tier applications. However, none of these vendors (as of yet) combines a comprehensive ability to monitor a variety of different applications architectures (J2EE, COM+, .Net, ASP, Citrix, etc.) for end user performance with an ability to help the problem resolution process once an application problem is identified.
  3. Problem resolution vendors (Identify Software, Mercury, Compuware, AviCode, XtremeSoft, etc.) offer a variety of capabilities to drill into specific source code environments and either pinpoint the problem or at least get the developer close to the source of the problem. However, these products are for the most part difficult to use in a "monitor all of the time mode" since they usually consume to much resource and generate too much data to be left on all of the time on every production server.

In summary the market opportunity for management of applications while they are in production is wide open. In order to seize this opportunity, someone will meet the requirements below and seize the brass ring:

  1. Monitor every aspect of the application no matter how it is architected (J2EE, .Net, etc.) and no matter where it runs.
  2. Collect meaningful performance data (response time) about every user of every application
  3. Operate in a manner consistent with the requirements of products that are running all of the time on all production servers (low resource utilization, and smart management of volumes of data produced)
  4. Automatically map the application components across the application system for each user of the application.
  5. Synthesize 1-4 above into true root cause reports that tell administrators and developers where the problems are and what to fix.

Someone will grab the brass ring and run off with a huge market opportunity. Who will it be?

Bernd Harzog
CEO
APM Experts
Bernd.harzog@APMExperts.com