January 2013 - logback-dev - mailman3.qos.ch

Custom Encoder issues
by Jeremy Pierre 29 Jan '13

29 Jan '13

Hi all, Cursory googling/ML search didn't turn anything up so I thought I'd ask a (possibly dumb) question. I'm working on a custom encoder (tried a LayoutBase as well, same issue described below) in order to output JSON formatted log messages. The reason I'm going down this particular route vs using the existing JSON layout extension is that for some messages, I need to append additional sub documents (log messages will go through logstash to ElasticSearch and possibly HDFS). My issue: I don't seem to be receiving "ERROR" level messages in my encoder although the same test code using a pattern layout seems to pass through error messages just fine. Simple encoder implementation (in Scala but should be intelligible regardless) follows, JSON stuff absent: class SimpleEncoder[T] extends EncoderBase[T] { override def close() {} override def doEncode(event: T) { event match { case loggingEvent: ILoggingEvent => { outputStream.write(loggingEvent.getArgumentArray().head.toString.getBytes()) outputStream.flush() } case other => { outputStream.write(s"OTHER: ${other}".getBytes()) outputStream.flush() } } } } logback.xml: <configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <encoder class="com.sample.logging.SimpleEncoder"/> </appender> <root level="DEBUG"> <appender-ref ref="STDOUT" /> </root> </configuration> Am I missing anything obvious? Thanks, Jeremy

1 0

[JIRA] (CONSPLUG-38) Flickering, disappearing tooltips
by Michał Politowski (JIRA) 29 Jan '13

29 Jan '13

1 0

[JIRA] (LOGBACK-801) Loading a logback config with different contextName throws IllegalStateException
by Joern Huxhorn (JIRA) 28 Jan '13

28 Jan '13

1 0

[JIRA] Created: (LBCORE-216) Add a layout that produces JSON
by Pierre Queinnec (JIRA) 25 Jan '13

25 Jan '13

Add a layout that produces JSON ------------------------------- Key: LBCORE-216 URL: http://jira.qos.ch/browse/LBCORE-216 Project: logback-core Issue Type: New Feature Components: Layout Affects Versions: 0.9.30 Reporter: Pierre Queinnec Assignee: Logback dev list Implement a layout producing JSON, possibly with no external dependencies. This enables having out-of-the-box experience connecting logback with external systems able to parse that format. I'll submit a patch as a pull request. For now this is commit : https://github.com/pmq/logback/commit/1161be30198ddca558363d92a282c7f975987… -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

5 5

[VOTING] logback-contrib license change
by Christian Trutz 25 Jan '13

25 Jan '13

Hello, we want to change the license of logback-contrib from Apache 2.0 license to EPL v1.0 / LGPL 2.1 license, to be in sync with the logback project. See also http://logback.qos.ch/license.html and https://github.com/qos-ch/logback-contrib/issues/1 logback-contrib has 6 contributors ( https://github.com/qos-ch/logback-contrib/graphs/contributors) belaso tony19 ceki lhazlewood nurkiewicz ejain @above contributors: Please vote, if the above license change from Apache to EPL/LGPL - is OK for you (+1) - is NOT OK for you (-1) Regards belaso

2 2

[JIRA] (LOGBACK-800) Concurrency Issue while rollover
by Chris Jones (JIRA) 24 Jan '13

24 Jan '13

1 0

[qos-ch/logback-extensions] c099e3: added m2e lifecycle-mapping plugin configuration s...
by Tony Trinh 24 Jan '13

24 Jan '13

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-extensions Commit: c099e39a4931a46f81e8ae06802c1f3ed310e1e8 https://github.com/qos-ch/logback-extensions/commit/c099e39a4931a46f81e8ae0… Author: Knute Axelson <kaxelson(a)gmail.com> Date: 2013-01-14 (Mon, 14 Jan 2013) Changed paths: M pom.xml Log Message: ----------- added m2e lifecycle-mapping plugin configuration so that the project can be imported to eclipse m2e without errors. this should have no negative effect on those using other ide's or doing command line maven builds. Commit: 03f1859b3c1a10e2db668f718b01fc9f73921733 https://github.com/qos-ch/logback-extensions/commit/03f1859b3c1a10e2db668f7… Author: Knute Axelson <kaxelson(a)gmail.com> Date: 2013-01-23 (Wed, 23 Jan 2013) Changed paths: M pom.xml M spring/src/main/java/ch/qos/logback/ext/spring/LogbackConfigurer.java Log Message: ----------- resolved NPE resulting from null ContextSelector happening because ContextSelectorBinder was not initialized. also made it possible to configure using either groovy or xml. previous implementation only worked with xml config. Commit: f93ab40e8e3b96922edb6ec519d5a1760cc3a660 https://github.com/qos-ch/logback-extensions/commit/f93ab40e8e3b96922edb6ec… Author: Tony Trinh <tony19(a)gmail.com> Date: 2013-01-23 (Wed, 23 Jan 2013) Changed paths: M pom.xml M spring/src/main/java/ch/qos/logback/ext/spring/LogbackConfigurer.java Log Message: ----------- Merge pull request #6 from kaxelson/master Fix to allow configuration through Spring using Groovy or XML Compare: https://github.com/qos-ch/logback-extensions/compare/3bc4b42722db...f93ab40…

1 0

[JIRA] Created: (LBCLASSIC-306) Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger
by Michael Pilquist (JIRA) 23 Jan '13

23 Jan '13

Mixing periods and dollar signs in a logger name causes IllegalArgumentException from LoggerFactory.getLogger ------------------------------------------------------------------------------------------------------------- Key: LBCLASSIC-306 URL: http://jira.qos.ch/browse/LBCLASSIC-306 Project: logback-classic Issue Type: Bug Affects Versions: 1.0.0 Reporter: Michael Pilquist Assignee: Logback dev list When mixing periods and dollar signs in a logger name, an IllegalArgumentException is thrown from LoggerFactory.getLogger: scala> org.slf4j.LoggerFactory.getLogger("a.b$c.d") java.lang.IllegalArgumentException: For logger [a] child name [a.b$c passed as parameter, may not include '.' after index2 at ch.qos.logback.classic.Logger.createChildByName(Logger.java:386) at ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:152) at ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:48) at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:253) Note that the following works: scala> org.slf4j.LoggerFactory.getLogger("a$b.c") res0: org.slf4j.Logger = Logger[a$b.c] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 4

[JIRA] (LOGBACK-799) Fix documentation for vararg syntax
by Mikhail Mazursky (JIRA) 23 Jan '13

23 Jan '13

1 0

[JIRA] (LOGBACK-758) NPE in JULHelper.asJULLevel() when setting a level back to null
by Brian Showers (JIRA) 17 Jan '13

17 Jan '13

2 2