[uplat] logging rewrite

[Heather Kreger <kreger@us.ibm.com>]

Here is my logging rewrite
1.1.1 Logging
1.1.1.1     What?

Logging is the action in which message producers generate log artifacts,
i.e., atomic expressions of diagnostic or activity information which is
stored in some persistent manner. Persistence may be temporary based on
policies or the configuration of the application. The log information may
or may not be used at a later time by other, independent, message consumers
for a variety of purposes.




1.1.1.2     Why?

Logged information is required for audit trails needed to fulfill judiciary
and organizational policy requirements, to reconcile security related
inconsistencies, and to provide for forensic evidence both after the fact
and real-time.  Logged information is also used as input to many management
applications, including but not limited to, service level monitoring,
capacity planning, usage mining, metering, billing, and problem
determination.

1.1.1.3     How?

There are two parts necessary to provide interoperable logging:


Programming model: Canonical logging Web service that a manageable service,
application using the service, or intermediary may invoke passing the log
information.


Infrastructure: Logging intermediary may watch messages flowing through a
system and log relevant information. The intermediary should use the
logging service to record data formatted as a CBE.


Format: Common Base Event log record format should be used to allow common
semantic understanding of the information in the event.

Heather Kreger
STSM, Web Services Lead Architect for SWG Emerging Technologies
Author of "Java and JMX: Building Manageable Systems"
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572