Date parsed: 7/30/2000 12:01:59 AM
Date: Sat, 29 Jul 2000 23:01:59 +0200


"Franz Krainer" <franzk@netal.com> wrote in message
news:3A25DBCDF73F2245957BD0B041BEDAF0015E35@is1.netal.com...
>
> > I may really be trying to piggyback on your Perfmon integration =
bug...
I
> > write an entry to the log and every request to invoke a server =
method.
> I'd
> > like to be able to use Perfmon to chart invocation velocities and
response
> > times.
> >
>
> It would be possible to enhance the PerfMon support for your needs, =
but
this
> feature wouldn't be really related to the functionality of a syslog
daemon.

Agreed.

>
> > I'd be happy to have even a password per channel.
>
> It's now on the feature list for the next version.
>

Great.

> > We include a session identifier with our log messages. On a busy
system,
> it
> > is difficult to view log message associated with just one session =
when
the
> > messages of many session are interleaved (especially in the Viewer).
I'd
> > like to either specify the channel within the message or configure =
the
> > logger to identify my session identifier and maintain a mapping =
between
it
> > and a dynamically allocated Viewer channel.
>
> Wouldn't it be sufficient for your needs to create some
'forward-to-viewer'
> actions, each one associated with a different channel, and then create
some
> rules, where you specify a text filter (your session id) and =
associate it
> an action (=3Dchannel)?
>

A session-id is dynamically generated when a user visits our website. =
We
use it to preserve web application session state information. We can =
not
know the sessions-id's in advance and even if we did it would not be
impractical to establish (say 1000) viewer rules for users yet to visit =
the
web site.