Yes, I agree that it is good to have more information in the log,
e.g the user-id etc.
Feel free to send a patch for the log formats to add this (you
can add all information available in the request object).
Carsten
> -----Ursprungliche Nachricht-----
> Von: Bernhard Huber [mailto:[EMAIL PROTECTED]]
> Gesendet: Mittwoch, 15. August 2001 22:22
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: [C2]: Unique request id
>
>
> Hi
> Generating log-entries with a unique request-id helps
> you as system-administrator to track everything for one
> incoming request.
> My experience to that sort of logging is that in an enterprise
> you have to add application data like user-id,too. And some
> department of wants to have logging entries not on the filesystem,
> but in an database, etc..
> Thus an application running under Cocoon, has to add logging entries
> adding the user-id.
>
> Thus there are a lot of different levels of logging...
> If LogKit can handle all that than it does a big job, and
> helps a lot!
>
>
> ----- Originalnachricht -----
> Von: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> Datum: Mittwoch, August 15, 2001 9:16 am
> Betreff: AW: [C2]: Unique request id
>
> > > Bernhard Huber wrote:
> > >
> > > Hi,
> > > What do hope to get by this unique request-id later?
> > > Aren't user-id more interesting, so you can figure out
> > > who has done what, http-request level may be too fine-grained.
> > The user-id (or ip-address) is of course very interesting
> > (if the user is not behind a firewall). It can already be
> > included in the log, as the Request/Response objects are
> > available in the log target.
> > But a unique request-id can be used to filter the log
> > to get all log entries which belong to one single request.
> > The id itself has no meaning.
> >
> > Carsten
> >
> > >
> > > ----- Originalnachricht -----
> > > Von: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> > > Datum: Dienstag, August 14, 2001 5:33 pm
> > > Betreff: [C2]: Unique request id
> > >
> > > > Hi,
> > > >
> > > > here another thought about logging:
> > > >
> > > > What about adding a unique identifier for the current request?
> > > > This would allow us to identify which log entries belong to
> > > > one single request. (Currently thread id and request uri
> > > > could be used, but are of course not very usefull as at a
> > > > later time the same thread id with the same request uri
> > > > could be invoked).
> > > >
> > > > Is there any value we could use for this provided by the
> > > > servlet api? If not what about adding a simple static
> > > > counter for this.
> > > >
> > > > Thoughts?
> > > >
> > > > Carsten
> > > >
> > > > ---------------------------------------------------------------
> > ----
> > > > --
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, email: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> >
> > -------------------------------------------------------------------
> > --
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, email: [EMAIL PROTECTED]
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
