March 2017 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1280) ${HOSTNAME} as FQDN
by QOS.CH (JIRA) 16 Mar '17

16 Mar '17

Roman T created LOGBACK-1280: -------------------------------- Summary: ${HOSTNAME} as FQDN Key: LOGBACK-1280 URL: https://jira.qos.ch/browse/LOGBACK-1280 Project: logback Issue Type: Improvement Environment: At the moment if we use HOSTNAME in our logback.xml, it is a short version of hostname. The problem with it, we've got two environments testing and production. In testing env we've got the server webservice-01.ipc00.pro00.eu.firm.com, on the other hand in production we've got webservice-01.ipc00.tst00.eu.firm.com . When the both sever write some logs in our kibana we can't make out, which server logs, because the hostname for both is webservice-01 If you would take for HOSTNAME InetAddress.html#getCanonicalHostName it would much better. PS. I know I can define PropertyDefiner and inject what I want, but it quite silly that the HOSTNAME variable doesn't work propertly in logback Reporter: Roman T Assignee: Logback dev list Priority: Minor -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1279) Async appenders do not scale well across multiple threads
by QOS.CH (JIRA) 13 Mar '17

13 Mar '17

1 0

[JIRA] (LOGBACK-1279) Async appenders do not scale well across multiple threads
by QOS.CH (JIRA) 13 Mar '17

13 Mar '17

1 0

[qos-ch/logback] 445637: minor editions
by Ceki Gulcu 13 Mar '17

13 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 44563701ff9bf0bc129cdbe88deb572386fa0236 https://github.com/qos-ch/logback/commit/44563701ff9bf0bc129cdbe88deb572386… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M logback-core/src/test/java/ch/qos/logback/core/rolling/helper/RollingCalendarTest.java M logback-site/src/site/pages/news.html Log Message: ----------- minor editions

1 0

[qos-ch/logback] 6e0c28: Fixed type within constant about incorrect attribu...
by Ceki Gulcu 13 Mar '17

13 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 6e0c28714d6026ed654f49601e3419612d0690d3 https://github.com/qos-ch/logback/commit/6e0c28714d6026ed654f49601e3419612d… Author: Andy Feller <afeller(a)bandwidth.com> Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/joran/action/ParamAction.java Log Message: ----------- Fixed type within constant about incorrect attribute for parameters Commit: b6b805574d5d188c85fe6a4de917ff7fb6558121 https://github.com/qos-ch/logback/commit/b6b805574d5d188c85fe6a4de917ff7fb6… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-13 (Mon, 13 Mar 2017) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/joran/action/ParamAction.java Log Message: ----------- Merge pull request #366 from andyfeller/paramaction_novalue_incorrect Fixed typo within constant about incorrect attribute for parameters Compare: https://github.com/qos-ch/logback/compare/8607f601e0ef...b6b805574d5d

1 0

[JIRA] (LOGBACK-1279) Async appenders do not scale well across multiple threads
by QOS.CH (JIRA) 13 Mar '17

13 Mar '17

Stephen Connolly created LOGBACK-1279: ----------------------------------------- Summary: Async appenders do not scale well across multiple threads Key: LOGBACK-1279 URL: https://jira.qos.ch/browse/LOGBACK-1279 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.2.1 Reporter: Stephen Connolly Assignee: Logback dev list Attachments: image-2017-03-13-12-10-55-553.png When running some benchmarking (specifically [https://github.com/stephenc/java-logging-benchmarks/blob/master/log4j-fmt/l…] - at time of issue creation @ceki has access to repo, but repo is due to become public soon) I noticed that the Async appender does not scale well when the number of threads increases. In fact the Async appender - which to my understanding is designed to help provide a more consistent latency under multiple threads - has dire performance when the number of threads increase, e.g. !image-2017-03-13-12-10-55-553.png! The above results show that Log4J with an async appender has a profile very similar to that of both Logback and Log4J with a non-asynchronous appender. Logback's asynchronous appender performance gets progressively worse and approximates the performance of Java Utils Logging above 16 threads on the test system -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 12 Mar '17

12 Mar '17

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 12 Mar '17

12 Mar '17

1 0

[JIRA] (LOGBACK-1277) Capping log files does not work with large log file base
by QOS.CH (JIRA) 12 Mar '17

12 Mar '17

1 0

[qos-ch/logback] 0e0dca: fix LOGBACK-1278
by Ceki Gulcu 12 Mar '17

12 Mar '17

Branch: refs/heads/master Home: https://github.com/qos-ch/logback Commit: 0e0dca96d326767bc03066703f877330cf3a36c0 https://github.com/qos-ch/logback/commit/0e0dca96d326767bc03066703f877330cf… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-12 (Sun, 12 Mar 2017) Changed paths: M logback-core/src/main/java/ch/qos/logback/core/util/FileSize.java M logback-core/src/test/java/ch/qos/logback/core/util/FileSizeTest.java M logback-site/src/site/pages/news.html Log Message: ----------- fix LOGBACK-1278 Commit: 8607f601e0ef8c6fd9b41f3e4ba9bff8dc0b2548 https://github.com/qos-ch/logback/commit/8607f601e0ef8c6fd9b41f3e4ba9bff8dc… Author: Ceki Gulcu <ceki(a)qos.ch> Date: 2017-03-12 (Sun, 12 Mar 2017) Changed paths: A logback-classic/src/test/input/joran/issues/logback-1277.xml A logback-classic/src/test/java/ch/qos/logback/classic/issue/logback_1277/Main.java M logback-core/src/main/java/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.java Log Message: ----------- work on LOGBACK-1277 Compare: https://github.com/qos-ch/logback/compare/49623d942a4f...8607f601e0ef

1 0