What format should I use?
I already tried "dd MM yyyy HH:mm:ss,SSS" but it didn't work. What should I
use to denote an actual month abbreviation as opposed to a numerical
representation? My conversionFormat for the timestamp in the Appender is
'%d{DATE}', not just %d. Any suggestions?
Thanks,
Matt
sdeboy wrote:
>
> Correct the timestamp format in the receiver config..that's probably the
> only issue.
>
> Scott Deboy
> Principal Engineer
> COMOTIV SYSTEMS
> 111 SW Columbia Street Ste. 950
> Portland, OR 97201
> Office: 503.224.7496
> Direct Line: 503.821.6482
> Cell: 503.997.1367
> Fax: 503.222.0185
> [EMAIL PROTECTED]
> www.comotivsystems.com
>
>
> -----Original Message-----
> From: bakermatt [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 19, 2008 5:36 PM
> To: [email protected]
> Subject: Re: How do receivers work?
>
>
> This is an extremely noob question but how do I setup my logFormat if my
> message looks like this:
>
> 19 Feb 2008 14:10:32,001 INFO DataCollectorTestAppender [main][]:
> LogMonitor - CanCaptureLogEvent
>
> Where:
>
> 19 Feb 2008 14:10:32,001 = TIMESTAMP
> INFO = LEVEL
> DataCollectorTestAppender = LOGGER
> [main] = THREAD
> [] = [*]
> LogMonitor - CanCaptureLogEvent = MESSAGE
>
> it is just "TIMESTAMP LEVEL LOGGER [THREAD][*]: MESSAGE" right? The
> receiver keeps giving me the "found non-matching line:" error. Perhaps
> my
> timeStampFormat is incorrect as yyyy-MM-d HH:mm:ss,SSS?
>
> Thanks,
> Matt
>
> Paul Smith-2 wrote:
>>
>>
>> On 20/02/2008, at 11:32 AM, bakermatt wrote:
>>
>>>
>>> Ok,
>>>
>>> So I got it so that the LoggingEvents get dispatched to my Appender
>>> but ALL
>>> of the Events get posted there, even the INFO and DEBUG events
>>> coming from
>>> the Receiver itself. How can I isolate the incoming messages from
> the
>>> messages being generated internally? Also, I am setting the
>>> LoggerRepository on the receivers to
> LogManager.getLoggerRepository().
>>> Should I create a new Hierarchy instance to isolate the Receivers
>>> from each
>>> other, or should I keep it the way it is?
>>>
>>>
>>
>> Just turn down the verbosity of the 'org.apache.log4j' top-level
>> logger as you would any other logger in your log4j configuration, that
>
>> way your custom appender never receives these events.
>>
>> Alternatively if the logging events you're really interested in come
>> from your own company code, say 'com.mycompany', you could attach your
>
>> custom appender that is processing these events to the logical top
>> level logger of interest, thereby bypassing any org.apache.log4j ones.
>>
>> cheers,
>>
>> Paul
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/How-do-receivers-work--tp15576255p15580474.html
> Sent from the Log4j - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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]
>
>
>
--
View this message in context:
http://www.nabble.com/How-do-receivers-work--tp15576255p15592364.html
Sent from the Log4j - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
