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

[JIRA] (LOGBACK-1660) Please add SyslogAppender that can connect to a unix socket
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1660) Please add SyslogAppender that can connect to a unix socket
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1662) PatternLayout: provide conversion keyword to access LoggingEvent#getSequenceNumber
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1657) LoggingEventV0 is loosing the nanoseconds
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1660) Please add SyslogAppender that can connect to a unix socket
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1656) Unused "nanoseconds" field in LoggingEvent
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1661) Mismatch between javadoc and default implementation for ILoggingEvent#getNanoseconds()
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] (LOGBACK-1659) Unnecessary OffsetDateTime creation in CachingDateFormat
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

1 0

[JIRA] Updates for LOGBACK-1664: Missing logs with ConsoleAppender
by QOS.CH (JIRA) 18 Aug '22

18 Aug '22

logback / LOGBACK-1664 [Open] Missing logs with ConsoleAppender ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1664 ============================== Issue created ------------------------------ rex created this issue on 18/Aug/22 11:19 AM Summary: Missing logs with ConsoleAppender Issue Type: Bug Assignee: Logback dev list Created: 18/Aug/22 11:19 AM Priority: Blocker Reporter: rex Description: My application is deployed on k8s,I write logs to console so that I can get logs with *kubectl logs -f*. I have a method with Java which will print info logs , now I find that sometimes we couldn't find logs with kubectl logs -f - missing logs. Below is my config: {noformat} <appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender"> <Target>System.out</Target> <encoder class="ch.qos.logback.core.encoder.LayoutWrappingEncoder"> <layout class="ch.qos.logback.contrib.json.classic.JsonLayout"> <jsonFormatter class="ch.qos.logback.contrib.jackson.JacksonJsonFormatter"> <prettyPrint>false</prettyPrint> </jsonFormatter> </layout> </encoder> <filter class="ch.qos.logback.classic.filter.ThresholdFilter"> <level>INFO</level> </filter> </appender> <root level="INFO" > <appender-ref ref="CONSOLE" /> </root>{noformat} ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0

[JIRA] Updates for LOGBACK-1663: LoggingEvent#sequenceNumber always 0 event after configuring a SequenceNumberGenerator
by QOS.CH (JIRA) 17 Aug '22

17 Aug '22

logback / LOGBACK-1663 [Open] LoggingEvent#sequenceNumber always 0 event after configuring a SequenceNumberGenerator ============================== Here's what changed in this issue in the last few minutes. This issue has been created This issue is now assigned to you. View or comment on issue using this link https://jira.qos.ch/browse/LOGBACK-1663 ============================== Issue created ------------------------------ Bertrand Renuart created this issue on 18/Aug/22 12:00 AM Summary: LoggingEvent#sequenceNumber always 0 event after configuring a SequenceNumberGenerator Issue Type: Bug Affects Versions: 1.3.0-beta0 Assignee: Logback dev list Components: logback-classic Created: 18/Aug/22 12:00 AM Priority: Major Reporter: Bertrand Renuart Description: The sequence number of logging events remains at 0 (zero) even after configuring a SequenceNumberGenerator in the LoggerContext. I tried to configure a sequence number generator in the logback.xml configuration file as follows: {code:xml} <configuration> <sequenceNumberGenerator class="ch.qos.logback.core.spi.BasicSequenceNumberGenerator"/> ... </configuration> {code} Although this configuration is accepted without error/warning, a call to LoggerContext#getSequenceGenerator() at runtime always returns null. After some investigations it appears that LoggerContext#getSequenceNumber() is *hardcoded to always return _null_* (see [here|http://example.com/] {code:java} public SequenceNumberGenerator getSequenceNumberGenerator() { return null; } {code} Also {{LoggerContext}} extends {{ContextBase}} which also maintains a reference to a SequenceNumberGenerator together with the associated setter and getter methods. Looks like there is some confusion about which class should own the generator... ============================== This message was sent by Atlassian Jira (v8.8.0#808000-sha1:e2c7e59)

1 0