- logback-user - mailman3.qos.ch

Problem with sizeAndTimeBasedRollingPolicy
by Ulrich Kriegel 07 Aug '24

07 Aug '24

Hi there, I tried to configure a SizeAndTimeBasedRollingPolicy programmatically (see below) Logger statisticsLogger = (Logger) LoggerFactory.getLogger("statistics"); int MAX_HISTORY = 1095; FileSize MAX_FILE_SIZE = FileSize.valueOf("250MB"); private static final String PATTERN = "%d %-5level %logger %msg%n"; LoggerContext loggerContext = (LoggerContext) LoggerFactory.getILoggerFactory(); String filename = "log/"+applicationContext.serviceGroupKey()+"-statistics.log"; String rollingFilenamePattern="log/"+applicationContext.serviceGroupKey()+"statistics-%d{yyyy-MM-dd_HH}.log.gz"; PatternLayoutEncoder patternLayoutEncoder = new PatternLayoutEncoder(); patternLayoutEncoder.setPattern(PATTERN); patternLayoutEncoder.setContext(loggerContext); patternLayoutEncoder.start(); RollingFileAppender<ILoggingEvent> rollingFileAppender = new RollingFileAppender<ILoggingEvent>(); rollingFileAppender.setFile(filename); rollingFileAppender.setName("statistics"); rollingFileAppender.setEncoder(patternLayoutEncoder); rollingFileAppender.setContext(loggerContext); rollingFileAppender.setImmediateFlush(true); rollingFileAppender.setAppend(false); patternLayoutEncoder.setParent(rollingFileAppender); SizeAndTimeBasedRollingPolicy<Object> rollingFilePolicy = new SizeAndTimeBasedRollingPolicy<>(); // TimeBasedRollingPolicy<Object> rollingFilePolicy = new TimeBasedRollingPolicy<>(); rollingFilePolicy.setContext(loggerContext); rollingFilePolicy.setParent(rollingFileAppender); rollingFilePolicy.setFileNamePattern(rollingFilenamePattern); rollingFilePolicy.setMaxHistory(MAX_HISTORY); rollingFilePolicy.setMaxFileSize(MAX_FILE_SIZE); // comment out for TimeBasedRollingPolicy rollingFilePolicy.start(); rollingFileAppender.setRollingPolicy(rollingFilePolicy); rollingFileAppender.start(); statisticsLogger.addAppender(rollingFileAppender); statisticsLogger.setAdditive(false); However, no logfile is produced. If the SizeAndTimeBasedRollingPolicy is replaced by a TimeBasedRollingPolicy, everything works fine. What is my mistake. Thanks in advance - Ulrich

1 0

POST data in log
by Matt Zagrabelny 17 Jun '24

17 Jun '24

Greetings, I'm attempting to configure a logback application (puppetdb) to log POST data, but I'm not seeing the options at: https://logback.qos.ch/manual/layouts.html#AccessPatternLayout I can get curl to output the POST data via --trace-ascii puppetdb# curl -H 'Content-type:application/json' -d '{ "query": ["extract", ["certname"], ["and", ["=", "type", "Class"], ["=", "title", "Postgresql::Server"] ] ] }' --trace-ascii - http://localhost:8080 /pdb/query/v4/resources == Info: Trying 127.0.0.1:8080... == Info: Connected to localhost (127.0.0.1) port 8080 (#0) => Send header, 153 bytes (0x99) 0000: POST /pdb/query/v4/resources HTTP/1.1 0027: Host: localhost:8080 003d: User-Agent: curl/7.88.1 0056: Accept: */* 0063: Content-type:application/json 0082: Content-Length: 111 0097: => Send data, 111 bytes (0x6f) 0000: { "query": ["extract", ["certname"], ["and", ["=", "type", "Clas 0040: s"], ["=", "title", "Postgresql::Server"] ] ] } <= Recv header, 17 bytes (0x11) 0000: HTTP/1.1 200 OK <= Recv header, 37 bytes (0x25) 0000: Date: Mon, 17 Jun 2024 19:49:24 GMT <= Recv header, 46 bytes (0x2e) 0000: Content-Type: application/json;charset=utf-8 <= Recv header, 35 bytes (0x23) 0000: Vary: Accept-Encoding, User-Agent <= Recv header, 20 bytes (0x14) 0000: Content-Length: 43 <= Recv header, 2 bytes (0x2) 0000: <= Recv data, 43 bytes (0x2b) 0000: [{"certname":"foo.example.com"}] [{"certname":"foo.example.com"}]== Info: Connection #0 to host localhost left intact I did add the '%fullRequest' option: <encoder> <pattern>%h %l %u [%t] "%r" %s %b "%i{Referer}" "%i{User-Agent}" %D %header{X-Uncompressed-Length} %fullRequest</pattern> </encoder> ...but I'm not seeing the POST data: 127.0.0.1 - - [17/Jun/2024:14:49:24 -0500] "POST /pdb/query/v4/resources HTTP/1.1" 200 43 "-" "curl/7.88.1" 12 - POST /pdb/query/v4/resources HTTP/1.1 Content-type: application/json Accept: */* User-Agent: curl/7.88.1 Host: localhost:8080 Content-Length: 111 Does anyone have any ideas how to see the POST data via logback? Thanks for the help! -m

1 0

JSON layout without logback-contrib?
by Gregg, John E. 17 May '24

17 May '24

I noticed that logback-contrib was archived in Git recently. Is there another way to do JSON layout? I looked at the source because profiling showed a lot of GC coming from the SimpleDateFormatter constructor used in JsonLayoutBase and was hoping to find a new version that reused DateTimeFormatter instead. Thanks

3 2

Custom MDC Implementations?
by Paul Galbraith 17 Apr '24

17 Apr '24

Is it possible to write your own custom MDC implementation (similar to log4j's ContextDataProvider) so that logback can get context details from something other than threadlocal storage?

3 3

Help with FileName and FilePAttern syntax:
by Aniruddha Shevade 29 Feb '24

29 Feb '24

Hello I am trying to migrate from log4j2 to logback. I am trying to find equivalent syntax for filename and filepatterns in this case log4j2.xml <RollingFile name="myLOg" *fileName="/log/${env1}-{{*myEnv|||@mydir@*}}-app.log"* .../> When i use something like this I get an exception saying invalid Repition. I m not sure what the above code was intended to do. 1. How can i convert this fileName to a valid one in logback ? 2. I do understand it will resolve ${env1} properly from environment variables. The "myENv" is being defined in a .properties file being loaded by the application. I have seens examples in logback.xml like <RollingFile name="myLOg" *fileName="/log/${env1}-:[myEnv]-app.log"* .../> what* does the :[myEnv] do here ? Would it resolve to a property set in a .* properties* file?* *ALso not sure what the @ symbol means in the log4j, and if it has any equivalent here?* thanks for any pointers Best Regards Ani

1 0

Xml to Java code, logstash encoder
by kypdk 14 Feb '24

14 Feb '24

Hello Guys I want to create the logstash encoder you see in xml with Java code. But there is no method to set the pattern. Which method should I do? <appender name="STASH" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>logback/uptLog.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy"> <fileNamePattern>logback/uptLog.%d{yyyy-MM-dd}.log</fileNamePattern> </rollingPolicy> <encoder class="net.logstash.logback.encoder.LogstashEncoder"> <charset>UTF-8</charset> <pattern> %d{yyyy-MM-dd HH:mm:ss.SSS} [%t] %-5level %logger{36} - %X{requestId} %msg%n%exception{full} </pattern> </encoder> </appender> net.logstash.logback.encoder.LogstashEncoder logstashEncoder = new LogstashEncoder(); logstashEncoder.setContext(loggerContext); logstashEncoder.start(); Regars

1 0

migration from log4j to logback. help with specific log4j.xml property (CronTriggerPolicy>
by Aniruddha Shevade 12 Feb '24

12 Feb '24

Hello I am trying to migrate a application form log4j to logback. I do have the following property defined in the existing log4j2.xml file, I do not see any such equivalent in the logback.xml. *How do I specify something like a CronTriggerPolicy as shown below?* Any help would be appreciated. log4j2.xml <RollingFile name="myLog" fileName="app.log" filePattern"app.log.%d{yyyyMMdd_HHmmzz}Z.log> <Policies> * <CronTiggerPolicy schedule="0 0 * * 1 ?" evaluateOnStartup="true">* <SizeBasedTriggerPolicy size="10MB"/> </Policies> </RollingFile> Best regards Ani

2 3

Is ContextSelector no longer used in 1.4?
by Michael Banks 12 Oct '23

12 Oct '23

We have recently updated to 1.4.11. Previously, we used the ContextJNDISelector for logging separation. In the latest LogbackServiceProvider, the code to make use of a ContextSelector is commented out and the defaultLoggerContext is always returned. public ILoggerFactory getLoggerFactory() { return defaultLoggerContext; // if (!initialized) { // return defaultLoggerContext; // // // if (contextSelectorBinder.getContextSelector() == null) { // throw new IllegalStateException("contextSelector cannot be null. See also " + NULL_CS_URL); // } // return contextSelectorBinder.getContextSelector().getLoggerContext(); } Is the concept of a ContextSelector now removed? Is there another mechanism for doing custom context selection?

1 0

Upgrading Logback Classic from 1.3.8 to 1.3.9 causes ClassNotFoundException: ch.qos.logback.classic.spi.Configurator
by dcmoeller＠gmx.de 29 Aug '23

29 Aug '23

Hello everybody, this morning weekly build of our software breaks with java.lang.ClassNotFoundException: ch.qos.logback.classic.spi.Configurator As we configure Gradle to apply runtimeOnly('ch.qos.logback:logback-classic:1.3+') this build receives new patch level version 1.3.9, published a few days ago. I've downloaded both versions, 1.3.8 and 1.3.9, of the lib from [1], missing class is available with 1.3.8, but missing in 1.3.9. General remark: I do not expect such a modification with patch level updates. My question: Is this a bug on your side, or have I missed some deprecation announcement explaining how to reconfigure Logback, or apply another Logback lib, or the like to avoid this problem? Thanks and regards Christian [1] https://mvnrepository.com/artifact/ch.qos.logback/logback-classic

2 5

logback-classic 1.4.9 removes public method
by Felix Krull 12 Aug '23

12 Aug '23

Hi, apparently logback-classic 1.4.9 removed the public method `configureByResource` from `ContextInitializer`, thereby breaking backwards compatibility? The method was removed in a commit [1] which made it into 1.4.9. It was deprecated in November of last year: I don't think this deprecation has ever been in a major release? Even if it had, I'd say it's poor form to remove deprecated things in a patch release. This breaks Play Framework [3] which uses the method for its logging setup, making it impossible to upgrade to this patch version. Regards, Felix [1]: https://github.com/qos-ch/logback/commit/4b06e062488e4cb87f22be6ae96e4d7d63… [2]: https://github.com/qos-ch/logback/commit/86f388965204df28843039f65b0bc437af… [3]: https://www.playframework.com/

3 3