Saturday, May 22, 2010

Amberpoint Amberpoint on the wall, who in the land is fairest of all?

I am reading the Introduction to Amberpoint Management System, I felt this absolutely touching, story of my life:

Monitoring this process that crosses application, container, and network boundaries
poses many challenges. Are users experiencing significant delays? Are faults being
generated? If transactions are failing, at what point are they failing? What is the dollar
cost per fault being generated? Typically, these questions can only be answered by
trolling through reams of log files gathered from distributed machines, potentially
owned by different development teams. Worse, this work is usually forensic in nature.
The transaction has already failed and there is little that can be done until all of the
logs are collected and the various teams have sorted through the problems. Any
corrections must go through the development and deployment process, further
magnifying the expense of time and money.

To address these challenges, the complete transaction should be visible in real time:
each cooperating piece of infrastructure and service should be able to obtain the
policies that indicate how requests should be treated and how to report information
about performance, errors, and conditions of interest to the business owner. One
possibility would be to have all SOA components (services, containers, logging
infrastructure, security infrastructure) provide standard management handles that
enable them to transmit performance and dependency information and to enforce
policies that align performance with business goals. Unfortunately, these standards do
not yet exist
. Even if they did exist, it is unlikely they could be sufficiently broad to
accommodate the heterogeneity of SOA or to anticipate component types yet to be
invented. An alternative solution would be to support management functions by
instrumenting the environment in which SOA applications run. By adding a
configurable management layer, it would be possible to retain all the advantages of
SOA design without incurring additional costs at production time.

No comments: