gnieh / logback-journal Goto Github PK
View Code? Open in Web Editor NEWsystemd journal appender for Logback
License: Apache License 2.0
logback-journal's People
Contributors
Stargazers
Watchers
Forkers
dcheckoway ataraxis abokth plumettaz subnova vijaykunapareddy takaomag xircleag dogukancagataylogback-journal's Issues
slf4j + logback-journal and systemd appender
Hi , I have a project that is using slf4j and logback-journal. Everything was working perfectly, however , I recently updated one of my dependencies, com.microsoft.azure.sdk.iot:iot-device-client:1.19 (gradle),
and then I started getting "No SLF4J Providers Found" warning. I solved the No providers warnings by updating my slf4j-api and slf4j-log4j12 versions to 1.8.0-beta4, but I am stilling getting a "No appenders could be found for logger (dao.hsqlmanager).
log4j:WARN Please initialize the log4j system properly"
It seems like my logback.xml file is not getting detected. Can someone please help me out?
logback.xml:
<configuration>
<appender name="journal" class="org.gnieh.logback.SystemdJournalAppender">
<encoder>
<pattern>%m%n</pattern>
</encoder>
</appender>
<root level="info">
<appender-ref ref="journal" />
</root>
</configuration>
gradle dependencies relevant to this question:
compile group: com.microsoft.azure.sdk.iot, name: iot-device-client, version: 1.19.1
compile group: org.slf4j, name: slf4j-api, version: 1.8.0-beta4
compile group: org.slf4j, name: slf4j-log4j12, version: 1.8.0-beta4
compile group: org.gnieh, name: logback-journal', version: 0.3.0
compileOnly group: org.projectlombok, name: lombok, version: 1.18.8
Logging exception stack trace
Is it possible to log the exception stack trace in the journal? There is such a possibility in log4j-systemd-journal-appender but I do not see an option to do that here.
EXN_STACKTRACE should contain nested exceptions
Quite often, higher-level code wraps exceptions thrown by lower-level code into their own exceptions. The stacktrace of the wrapping exception then only contains the higher-level location where the wrapping exception was thrown, not the lower-level location where the original exception happened.
Usually logging appenders resolve this problem by showing the wrapped exception and some of its stacktrace below the trace of the wrapping exception, separated by a "Caused by..." line (or similar).
It would be good to have this here, too.
stacktrace longer than 4096 characters turns into NULL
I've been playing around with this repo and found that some of my stacktraces are 'null'.
I try using substring and found that if it's 4095 it works, and 4096 doesnt.
Is this a systemd limitation? Any tips?
Could not find artifact org.gnieh:logback-journal:jar:0.1.0-SNAPSHOT
I'm trying to build a project with logback-journal, but apparently it's not found on maven repo, and the build fails with: Could not find artifact org.gnieh:logback-journal:jar:0.1.0-SNAPSHOT
UnsatisfiedLinkError: Unable to load library 'libsystemd-journal'
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unable to load library 'libsystemd-journal': Native library (linux-x86-64/liblibsystemd-journal.so) not found in resource path ([…])
at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:271)
at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:398)
at com.sun.jna.Library$Handler.<init>(Library.java:147)
at com.sun.jna.Native.loadLibrary(Native.java:412)
at com.sun.jna.Native.loadLibrary(Native.java:391)
at org.gnieh.logback.SystemdJournalLibrary.<clinit>(SystemdJournalLibrary.java:30)
at org.gnieh.logback.SystemdJournalAppender.append(SystemdJournalAppender.java:97)
at org.gnieh.logback.SystemdJournalAppender.append(SystemdJournalAppender.java:1)
at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:85)
at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48)
at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:273)
at ch.qos.logback.classic.Logger.callAppenders(Logger.java:260)
at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:442)
at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:396)
at ch.qos.logback.classic.Logger.info(Logger.java:600)
at org.gnieh.logback.TestSimple.main(TestSimple.java:15)
README.md: Tell defaults of boolean config options
Please add something like "Defaults to true" to the description of logLocation and the like.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.