Date parsed: 7/20/2000 5:32:22 PM
Date: Thu, 20 Jul 2000 16:32:22 +0200

1. Ability to break message text into multiple fields for the ODBC log
target.
2. Perfmon user definable counters measuring velocity and counts of
specific message text patterns.
3. Some basic authentication for access to the Telnet (Viewer); =
Ideally
linked to an NT Authentication role. Authentication should be required
either globally and/or by Viewer channel.
4. Dynamic selection of Viewer channel based on information in the =
message
text.
5. COM component log target (plug-in) for custom extensibility. If I =
had
this, I could implement #1 and #2 myself.

#1 and #5 are the most important to me. Our application generates a lot =
of
structured event information that then gets flatted to the syslog =
message
text. We then have to do post processing on the logs to regain the
structured information for reporting and analysis. We could use a COM
interface for custom handling of events that better integrate with the
applications runtime environment.
#3 addresses protection of possibly sensitive information in an =
production
environment. If I have this, I'd then also want some protection (I =
know,
doesn't conform to syslog spec) for data on the wire.
#4 would give us the ability to zero in on log message trigger by =
actions
for a single user session in a multi-user environment.
#2 is a nice-to-have feature that would allow use to use Perfmon and =
SL4NT
to monitor performance and events across all machines in a distributed
environment.


Tell me your thoughts.