cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Customer Care <customer.c...@mi8.com>
Subject FW: AW: [C2]: Unique request id
Date Thu, 16 Aug 2001 14:57:40 GMT


-----Original Message-----
From: Bernhard Huber [mailto:bh22351@i-one.at]
Sent: Wednesday, August 15, 2001 4:22 PM
To: cocoon-dev@xml.apache.org
Subject: 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" <cziegeler@sundn.de>
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" <cziegeler@sundn.de>
> > 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: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> > >
> >
>
> -------------------------------------------------------------------
> --
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>



**********************************************************************

Mi8 Powered Applications - Brains for Business

**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been
scanned for the presence of computer viruses.

**********************************************************************

Mime
View raw message