June 2012 - logback-user - mailman3.qos.ch

Websphere specific JMX configuration?
by Sumanth Donthi 12 Jun '12

12 Jun '12

How can we enable JMX for logback in WebSphere ? Currently do not see ch.qos.logback.classic.jmx.Configurator in jconsole though <jmxConfigurator/> tag exist in logback configuration file. logback 0.9.27 WebSphere 7.0 This is similar to one posted earlier -- http://www.qos.ch/pipermail/logback-user/2010-November/001886.html -Sumanth

4 6

Re: [logback-user] LocLoggers and TurboFilters
by Dario Campagna 12 Jun '12

12 Jun '12

Hi Ceki, > Could you provide a code sample of how you invoke a LocLogger with a marker? Sure! The following class shows how I use a LocLogger to generate a logging request with a marker. public class LocLoggerTest { public static void main(String[] args) { IMessageConveyor mc = new MessageConveyor(Locale.getDefault()); LocLoggerFactory llFactory_default = new LocLoggerFactory(mc); LocLogger locLogger = llFactory_default.getLocLogger("defaultLocLogger"); Marker alwaysMarker = MarkerFactory.getMarker("ALWAYS"); locLogger.info(alwaysMarker,"This will always appear."); locLogger.info("Hello!"); } } A simple configuration file to test it is <configuration debug="true"> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder> <pattern>%level - %date - %marker - %msg%n</pattern> </encoder> </appender> <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Marker>ALWAYS</Marker> <OnMatch>ACCEPT</OnMatch> <OnMismatch>NEUTRAL</OnMismatch> </turboFilter> <logger name="defaultLocLogger" level="INFO"> <appender-ref ref="STDOUT" /> </logger> </configuration> When I change the logger level to a value grater than INFO, the logging request marked ALWAYS is not enabled. Cheers, Dario

2 2

Log rollover: activate based on size but keep "creation date" in file name?
by Yura Levandovskyy 11 Jun '12

11 Jun '12

Hello, I'm trying to configure a naming scheme that would result in longs in the format of %d{yyyy-MM-dd-HHmm}.%i.log, however the time should indicate log creation time, not current time. New log is created in 2 situations: on application launch <rolloverOnStart>true</rolloverOnStart> or <maxFileSize>1MB</maxFileSize>. However, because of the naming format, the log gets put in a different location every minute. Is there a way to only set the log name on creation and then write to it until next rollover? Thank you

2 2

Re: [logback-user] LocLoggers and TurboFilters
by Dario Campagna 11 Jun '12

11 Jun '12

Hi Ceki, > The Please file bug report so that this issue can be tracked. You can > file the bug report in logback or slf4j (the bug is actually in > slf4j-ext). I filed a bug report in slf4j. Cheers, Dario

1 0

one mail within 10 new log entries
by atillademirel＠gmail.com 10 Jun '12

10 Jun '12

Hi all, I made a conf at least, But I want to get one mail within 10 new log entries, The following conf, I get 10 entry but whenever one log entry comes, immediately one mail with 1 new entry and 9 old one. How can I get one mail within 10 new entries ? Regards, <appender name="EMAIL" class="ch.qos.logback.classic.net.SMTPAppender"> <filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator> <expression>return message.contains("vpn");</expression> </evaluator> <OnMismatch>NEUTRAL</OnMismatch> <OnMatch>DENY</OnMatch> </filter> <smtpHost>10.x.x.x</smtpHost> <to>atilla.demirel(a)gmail.com</to> <from>tapi(a)throne.com.tr</from> <subject>TAPI:${hostname}: %logger{20} - %m</subject> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="ch.qos.logback.classic.html.HTMLLayout"> <pattern>%date %-5level %logger{35} - %message%n</pattern> </layout> </encoder> <cyclicBufferTracker class="ch.qos.logback.core.spi.CyclicBufferTrackerImpl">  <bufferSize>10</bufferSize> </cyclicBufferTracker> </appender> Bu e-posta, Turkcell BlackBerry ile gönderilmiştir.

1 0

help - Can I configure logback from outside of the package? So I could change configuration without rebuid the package?
by shan shan 08 Jun '12

08 Jun '12

Part of my logback.xml file is like that > <logger name="APICallLogger" level="INFO"> > <appender-ref ref="API_CALL_LOGGER" /> > </logger> > > May I configure the log level outside of the package at runtime? > So everytime when I need to reset the Log level, I don't need to rebuild > the whole package. > Are there any way I can do it? Thanks very much for any ideas or > suggestions. >

1 0

LocLoggers and TurboFilters
by Dario Campagna 08 Jun '12

08 Jun '12

Hi all, Some days ago I started using LocLogger instead of Logger instances in my application in order to generate localized logging events. The configuration file I am using contains two MarkerFilters to always enable certain logging requests. For example, the marker filter <turboFilter class="ch.qos.logback.classic.turbo.MarkerFilter"> <Marker>INFO_LOG</Marker> <OnMatch>ACCEPT</OnMatch> <OnMismatch>NEUTRAL</OnMismatch> </turboFilter> always enable logging requests marked INFO_LOG. Thanks to it, when using Loggers, logging requests marked INFO_LOG are enabled even when the logger level is set to OFF. Since I moved from Loggers to LocLoggers these filters stopped working, i.e., it seems that they are not used to determine if a logging request is enabled or not. With LocLoggers logging requests marked INFO_LOG are disabled when the logger level is set to OFF. Is this a known issue? Is there a way to solve it? Cheers, Dario

2 1

ANSI coloring?
by ceki 07 Jun '12

07 Jun '12

Hello all, Has anyone had a chance to try ANSI coloring [1] as introduced in logback 1.0.5? It's a seemingly cool feature but I am curious whether it's actually useful. [1] http://logback.qos.ch/manual/layouts.html#coloring -- Ceki http://twitter.com/#!/ceki

3 6

DBAppender ability to self prune database logging tables
by Smith, Larry (ECS - Enterprise Cloud Service) 07 Jun '12

07 Jun '12

I would like to be able to clean up logging entries written to the database. In many of our environments developers test on local copies of databases and in our function test environment we have daily build and deploys of the application. Needless to say, there can be a lot of logging in early stages of development and the log files can grow quite large. I would like to do something similar to the HISTORY tag associated with the rolling file appender, where you could specify how many days, weeks, months that you would like to keep entries in the logging tables. This needs to be something done from the application, as we do not have the ability to run scheduled database jobs in the various environments to automatically clean up database entries (this is a management procedure, won't bore you with details). Larry Smith

1 0

use property substitution for login credential in logback.xml from tomcat context.xml
by stephen.t.chan＠asia.bnpparibas.com 07 Jun '12

07 Jun '12

Hi all, I am running tomcat6 as http server and specify jdbc connection(with login credential) in context.xml. Besides, I have defined to use DBAppender in logback.xml to write log to database. My question is, instead of directly write the login credential in the logback.xml file, how to use property substitution to retrieve the credential from tomcat context.xml? for example, <appender name="DB" class="com.eqd.iprice.appender.DBAppender"> <connectionSource class= "ch.qos.logback.core.db.DriverManagerConnectionSource"> <dataSource class="javax.sql.DataSource"> <driverClass>${driverClass}</driverClass> <url>${url}</url> <user>${username}</user> <password>${password}</password> </dataSource> </connectionSource> </appender> Those ${XXXX} are retrieved from tomcat context.xml . Thanks. Stephen This message and any attachments (the "message") is intended solely for the intended addressees and is confidential. If you receive this message in error,or are not the intended recipient(s), please delete it and any copies from your systems and immediately notify the sender. Any unauthorized view, use that does not comply with its purpose, dissemination or disclosure, either whole or partial, is prohibited. Since the internet cannot guarantee the integrity of this message which may not be reliable, BNP PARIBAS (and its subsidiaries) shall not be liable for the message if modified, changed or falsified. Do not print this message unless it is necessary,consider the environment. ------------------------------------------------------------------------------------------ Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur ou s'il ne vous est pas destine, merci de le detruire ainsi que toute copie de votre systeme et d'en avertir immediatement l'expediteur. Toute lecture non autorisee, toute utilisation de ce message qui n'est pas conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite. L'Internet ne permettant pas d'assurer l'integrite de ce message electronique susceptible d'alteration, BNP Paribas (et ses filiales) decline(nt) toute responsabilite au titre de ce message dans l'hypothese ou il aurait ete modifie, deforme ou falsifie. N'imprimez ce message que si necessaire, pensez a l'environnement.

2 1