Skip to Content.
Sympa Menu

perfsonar-dev - Re: [pS-dev] eXist logging information in the SSHTELNET MP logs

Subject: perfsonar development work

List archive

Re: [pS-dev] eXist logging information in the SSHTELNET MP logs


Chronological Thread 
  • From: Guilherme Fernandes <>
  • To: Michael Bischoff <>
  • Cc: Stijn Melis <>, Roman Lapacz <>, "" <>
  • Subject: Re: [pS-dev] eXist logging information in the SSHTELNET MP logs
  • Date: Wed, 18 Jun 2008 18:02:21 +0200
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=wZFgtGoJErkKPALqHY8w3oq2IV9HeojKllRmuDDcLi4jBwGAUGLw6JFXwFvTmzLaKx vy/YbK9EMmDi291k/CQ9+56AqRvpHVbGk08PlXx5gB/mspDpOP9yGucfLOU0AZDCMlUV ruJZ2r0mkXBtzwXT4TjpGYXRXNDLEPf1tP1E4=

Michael Bischoff wrote:
Hallo all,

Hi,
I'd hate to burst your(our) bubble but because of the way logging is run as
an auxiliary
component it registers the log statement as coming from the auxiliary
component and thus
you can't filter the results based upon which component(more correct:
package) they come
from.

For the debug level there was an "unspoken standard" to include the class/component name in the debug message, filtering could be done based on this (the actual auxiliary component should just be ignored). For the other levels I don't think this is a pertinent issue (the user should have to know which component is sending the messages).

Of course this solution is cumbersome, all the developers need to take notice and remember to add it to every log.debug call. It would be nicer to have it done automatically by the logger component. Is that what you mean by "to accommodate filtering"?

Regards,

Guilherme


This is a serious?, well at least very tedious flaw in the current perfsonar
base.

I hope this is addressed in the new perfsonar base prototype.

Hmm I'm writing this message I wondered how http://www.slf4j.org/ fixes this.

I stumbled upon this:
http://svn.slf4j.org/viewvc/slf4j/trunk/slf4j-log4j12/src/main/java/org/slf4j/impl/Log4jLoggerAdapter.java?view=markup

/**
* Following the pattern discussed in pages 162 through 168 of "The complete
* log4j manual".
*/
final static String FQCN = Log4jLoggerAdapter.class.getName();

I fixed the base to accommodate filtering when using log4j.

I'll see if I can upload a new version soon.

Kind regards,

Michael Bischoff

Maybe we should implement a "perfsonar base debugging level". It can be
easily done with log4j, and both would actually log as DEBUG level, but we
can then choose
if we want only the debug info from our implementation, only the one from
base, or both..
This seems like a good idea, although in practice I would probably still
enable both most of the time (to see if the Authentication and LS
Registration works for
example).

I can just remove the lines which are of no interest to me using some
text editor, this would fix my problem as well :)

Cheers,


Stijn


Guilherme

Cheers,


Stijn


Roman


Thanks in advance,


Stijn







Archive powered by MHonArc 2.6.16.

Top of Page