August 2022 - logback-user - mailman3.qos.ch

Re: [logback-user] logback-user Digest, Vol 126, Issue 5
by Thomas Schittli 31 Aug '22

31 Aug '22

Thank you **very** much, Ceki Gülcü, for your support: Hi Thomas, SiftingAppender is probably what you are looking for. https://logback.qos.ch/manual/appenders.html#SiftingAppender -- Ceki Gülcü it works perfectly and is quite great 😊 Thanks a lot, kind regards, Thomas -----Original Message----- From: logback-user <logback-user-bounces(a)qos.ch> On Behalf Of logback-user-request(a)qos.ch Sent: Wednesday, August 31, 2022 12:00 PM To: logback-user(a)qos.ch Subject: logback-user Digest, Vol 126, Issue 5 Send logback-user mailing list submissions to logback-user(a)qos.ch To subscribe or unsubscribe via the World Wide Web, visit http://mailman.qos.ch/mailman/listinfo/logback-user or, via email, send a message with subject or body 'help' to logback-user-request(a)qos.ch You can reach the person managing the list at logback-user-owner(a)qos.ch When replying, please edit your Subject line so it is more specific than "Re: Contents of logback-user digest..." Today's Topics: 1. Logback FileAppender question: is it able to create log filenames dynamically by a string passed e.g. in LOGGER.trace()? (Thomas Schittli) 2. Re: Logback FileAppender question: is it able to create log filenames dynamically by a string passed e.g. in LOGGER.trace()? (Ceki Gülcü) ---------------------------------------------------------------------- Message: 1 Date: Tue, 30 Aug 2022 12:59:56 +0000 To: "logback-user(a)qos.ch" <logback-user(a)qos.ch> Subject: [logback-user] Logback FileAppender question: is it able to create log filenames dynamically by a string passed e.g. in LOGGER.trace()? Message-ID: <DB7PR04MB44577D12DBC68188909E3C13BD799(a)DB7PR04MB4457.eurprd04.prod.outlook.com> Content-Type: text/plain; charset="utf-8" Good afternoon The documentation for SLF4J and Logback is very detailed 😊, but unfortunately it is still difficult to understand the various possibilities and mechanisms, so I have a question: Is it possible to configure the logback FileAppender so that it automatically / dynamically creates logfile names based on a string which the developer passes in e.g. LOGGER.trace()? The background to the idea is as follows: 1. The developer is programming a new module (e.g. a configuration manager) and he would like to have the log entries summarised in a separate log file. 2. Therefore, he calls something like that: LOGGER.trace(“Config-Mgr”, “Message”) 3. SLF4J / Logback automatically reads this string and create this Logfile: AppLog-Config-Mgr.log 4. The central element is that we do not have to modify logback.xml and create an appender for each Logfile. This means that if the user now calls e.g.: LOGGER.trace(“User-Actionlog”, “Message”) then this new log file will created without having to modify logback.xml: AppLog-User-Actionlog.log Thank you very much for any tips & tricks 😊 Thanks a lot, kind regards, Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20220830/4df874c5/…> ------------------------------ Message: 2 Date: Tue, 30 Aug 2022 21:26:44 +0200 To: logback-user(a)qos.ch Subject: Re: [logback-user] Logback FileAppender question: is it able to create log filenames dynamically by a string passed e.g. in LOGGER.trace()? Message-ID: <5b9c4fee-2451-bcc7-f9ad-c0af38e48a73(a)qos.ch> Content-Type: text/plain; charset=UTF-8 Hi Thomas, SiftingAppender is probably what you are looking for. https://logback.qos.ch/manual/appenders.html#SiftingAppender -- Ceki Gülcü Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch On 8/30/2022 2:59 PM, Thomas Schittli wrote: > Good afternoon > > > > The documentation for SLF4J and Logback is very detailed 😊, but > unfortunately it is still difficult to understand the various > possibilities and mechanisms, so I have a question: > > > > Is it possible to configure the logback FileAppender so that it > automatically / dynamically creates logfile names based on a string > which the developer passes in e.g. LOGGER.trace()? > > > > The background to the idea is as follows: > > > > 1. The developer is programming a new module (e.g. a configuration manager) > and he would like to have the log entries summarised in a separate > log file. > > 2. Therefore, he calls something like that: LOGGER.trace(“Config-Mgr”, > “Message”) > > 3. SLF4J / Logback automatically reads this string and create this > Logfile: AppLog-Config-Mgr.log > > > 4. The central element is that we do not have to modify logback.xml and > create an appender for each Logfile. > > This means that if the user now calls e.g.: > LOGGER.trace(“User-Actionlog”, “Message”) > then this new log file will created without having to modify > logback.xml: > AppLog-User-Actionlog.log > > > > > Thank you very much for any tips & tricks 😊 > > Thanks a lot, kind regards, > Thomas > > ------------------------------ Subject: Digest Footer _______________________________________________ logback-user mailing list logback-user(a)qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user ------------------------------ End of logback-user Digest, Vol 126, Issue 5 ********************************************

1 0

Logback FileAppender question: is it able to create log filenames dynamically by a string passed e.g. in LOGGER.trace()?
by Thomas Schittli 30 Aug '22

30 Aug '22

Good afternoon The documentation for SLF4J and Logback is very detailed 😊, but unfortunately it is still difficult to understand the various possibilities and mechanisms, so I have a question: Is it possible to configure the logback FileAppender so that it automatically / dynamically creates logfile names based on a string which the developer passes in e.g. LOGGER.trace()? The background to the idea is as follows: 1. The developer is programming a new module (e.g. a configuration manager) and he would like to have the log entries summarised in a separate log file. 2. Therefore, he calls something like that: LOGGER.trace(“Config-Mgr”, “Message”) 3. SLF4J / Logback automatically reads this string and create this Logfile: AppLog-Config-Mgr.log 4. The central element is that we do not have to modify logback.xml and create an appender for each Logfile. This means that if the user now calls e.g.: LOGGER.trace(“User-Actionlog”, “Message”) then this new log file will created without having to modify logback.xml: AppLog-User-Actionlog.log Thank you very much for any tips & tricks 😊 Thanks a lot, kind regards, Thomas

2 1

Release of logback versions 1.3.0 and 1.4.0
by Ceki Gülcü 28 Aug '22

28 Aug '22

Hello all, I am thrilled to announce the simultaneous release of logback versions 1.3.0 and 1.4.0. Both versions require slf4j-api version 2.0.0 or later. Given that downstream users are likely to depend on either Java EE (in the javax namespace) or on Jakarta EE (in the jakarta namespace) in their projects, it was deemed important for logback to support both EE alternatives. As such, logback 1.3.x supports Java EE whereas logback 1.4.x supports Jakarta EE, otherwise the two versions are feature identical. Both 1.3.x and 1.4.x series require the fluent-API introduced in SLF4J 2.0.x. The 1.3.x series requires Java 8 at runtime. If you wish to build logback from source, you will need Java 9. Reproducible builds require Java 18. The 1.4.x series requires Java 11 at build time and at runtime. ------------------ Joran, logback's configuration system, has been rewritten to use an internal representation model which can be processed separately. Given the breadth of the changes, support for SiftingAppender was dropped temporarily and reintroduced in logback version 1.3.0-alpha16. Support for Groovy configuration was dropped for security reasons but was recovered by Tucker Pelletier (virtualdogbert). See: https://github.com/virtualdogbert/logback-groovy-config For benchmarking figures please see: http://logback.qos.ch/performance.html Recent logback releases are reproducible. This means that anyone checking out the code corresponding to the release version from github and building that local copy, will get obtain an identical binary to the binary found on Maven central. Note that due to issue MJAR-275 with the module-info.java produced in earlier java versions, reproducible builds require Java 18. Donations and sponsorship You can also support SLF4J/logback/reload4j projects via donations and sponsorship. We thank our current supporters and sponsors for their continued contributions. Sponsorship link: https://github.com/sponsors/qos-ch?o=esb Announcement mailing list: You can receive SLF4J/logback/reload4j related announcements by subscribing QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki Gülcü

1 0

Strategy for supporting both Java EE and Jakarta EE in logback distributions
by Ceki Gülcü 25 Aug '22

25 Aug '22

Hello all, I just started a discussion on supporting both Java EE and Jakarta EE in logback. Here is the link: https://github.com/qos-ch/logback/discussions/585 Do not hesitate to chime in. -- Ceki Gülcü Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch

1 0

Required Logback.xml utility
by Vijayakrishna Boggavarapu 12 Aug '22

12 Aug '22

Hi Team, How are you? Hope everything is going well on your end. We are searching for a tool similar to a jar or shell script that can convert a log4j.properties file into a logback.xml file after receiving it from the user. Please let us know if you have a utility or any specific instructions we can follow to convert the log4j.properties file to a logback.xml one. Thanks, Vijayakrishna DevOps Engineer Sr., WFM [cid:image001.png@01D8AE78.6D690FA0]<https://www.credly.com/badges/96317f21-42d3-4d05-a266-2db5657a8936/public_u…>

2 2