How about calling the subAppend(LoggingEvent) method within your appender? That
would prevent the append() method from being called recursively since your disk
utilization check is located there.
(Embedded image moved to file: pic15141.jpg)
"Bruno Melloni"
<[EMAIL PROTECTED]
.com> To
"Log4J Users List"
09/11/2008 02:02 PM <[email protected]>
cc
Please respond to Subject
"Log4J Users List" RE: Logging from appender
<[EMAIL PROTECTED]
.apache.org>
The disk utilization check is called form inside the 'append' process...
that is why it would be messy.
As I said in the original email, there probably is a specific Log
class/method already in log4j intended for logging from inside an
appender. It would be consistent with log4j's design. But I can't seem
to find that class/method.
Thanks for trying anyway.
bruno
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 11:21 AM
To: Log4J Users List
Subject: RE: Logging from appender
I'm using a RollingFileAppender in my logging. It extends FileAppender,
which extends WriterAppender. The WriterAppender has an "append" method
which takes a LoggingEvent object as a parameter. Is your appender a
subclass of WriterAppender or some other class that extends
WriterAppender? You could maybe call the "append" method and send your
LoggingEvent?
Again, I'm fairly new to log4j.
(Embedded image moved to file: pic11478.jpg)
"Bruno Melloni"
<[EMAIL PROTECTED]
.com>
To
"Log4J Users List"
09/11/2008 12:13 PM <[email protected]>
cc
Please respond to
Subject
"Log4J Users List" RE: Logging from appender
<[EMAIL PROTECTED]
.apache.org>
Sorry, I think I got misunderstood. I have no problem with
levels/thresholds when logging from the app.
What I want to do is generate an additional log message from INSIDE the
appender code, WHILE it is about to process an application message.
bruno
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 10:59 AM
To: Log4J Users List
Subject: Re: Logging from appender
I'm not an expert on Log4j, but recently had a similar requirement. I
didn't want debug messages appearing on the console. So on my console
appender, I set a threshold like this:
log4j.appender.CA.Threshold=INFO
I got that from somebody else on this list. This way I only see INFO
messages and above on the console and I see everything in my log file
from debug up. If you did the same but set the threshold above WARN,
the console will only show messages above WARN, however you won't see
anything less than or equal to WARN on the console. Don't know if that
helps. I think the log4j configuration in XML allows for a min and max
threshold.
(Embedded image moved to file: pic17673.jpg)
"Bruno Melloni"
<[EMAIL PROTECTED]
.com>
To
"Log4J Users List"
09/11/2008 11:53 AM <[email protected]>
cc
Please respond to
Subject
"Log4J Users List" Logging from appender
<[EMAIL PROTECTED]
.apache.org>
What is the best way to send a message to the log from inside the
Appender itself? (separate from the message that the appender is
currently processing)
Why do I even ask this? My appender checks disk utilization every hour.
I'd like to record the % of disk utilized in the log.
I tried using LogLog.warn(), but it puts the message on the console, not
in the log file generated by the appender. I could probably add it
manually to the code that writes to the file, but that feels messy...
and I suspect that there's built-in log4j functionality for what I want
to do.
bruno
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
