logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Wiwchar" <michaelwiwc...@hotmail.com>
Subject Re: Locating log entries
Date Mon, 21 Jan 2002 18:31:50 GMT
We have built a class LogMessage that allows for the building messages in
different format's, one format is a key-pair the LogMessage builds a key
that starts the message. The LogMessage key typically starts with the
abbreviation of the originating Class name - then a 4 digit number ( you
could use a larger number )  that identifies a specific code block within
the class. We then inform the user of the specific error message key and
repository name and they can then send that to us.
----- Original Message -----
From: <nigel.d.watson@hsbcgroup.com>
To: <log4j-user@jakarta.apache.org>
Sent: Monday, January 21, 2002 12:22 PM
Subject: Locating log entries

> When we get problems in carrying out a request, we want to use log4j to
> report the problem.
> When the original request comes from a user we want to be able to tell the
> user where the problem log is located without having to send them the
> details of the problem.
> This will allow them to contact IT support personnel with something
> For example the  ideal would be a file name and a line number, or more
> generically, a repository name and a unique key for the log entry in that
> repository.
> The file Appenders in log4j will return the file name, but is there anyway
> of finding the line number in the file when a message is logged, or of
> making log4j appenders generate a key?
> Regards,
> Nigel
> The HSBC Group's website is at http://www.hsbc.com
> _____________________________________________________
> HSBC Bank Plc, which is regulated in the UK by FSA, has issued the
> information contained in this message (including any attached
> documents) for its institutional and professional customers only.
> It is not intended for private customers. This message and any
> attachments are not an invitation to buy or sell securities or related
> financial instruments, are confidential to the named recipient and may
> also be priviledged. The information should not be reproduced and / or
> distributed to any other person. Internet communications are not secure
> and HSBC Bank Plc makes no representation and accepts no
> responsibility or liability as to the completeness and accuracy of the
> information contained in this message. Each page attached hereto
> must be read in conjunction with any disclosure which forms part of it.
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>

View raw message