jenkins.war manually with
java -jar jenkins.war,
all logging information by default is output to standard out. Many
Jenkins native packages modify this behavior to ensure logging
information is output in a more conventional location for the platform.
By default logs should be made available in
/var/log/jenkins/jenkins.log, unless customized in
/etc/default/jenkins (for *.deb) or via
By default logs should be at
%JENKINS_HOME%/jenkins.err, unless customized in
Log files should be at
java.util.logging for logging. The
java.util.logging system by
default sends every log above
INFO to stdout.
Jenkins is equipped with a GUI for configuring/collecting/reporting log records of your choosing. This page shows you how to do this.
First, select the "System Log" from the "Manage Jenkins" page:
From there, you can create a custom log recorder, which helps you group relevant logs together while filtering out the noise.
Choose a name that makes sense to you.
You’ll be then asked to configure loggers and their levels whose output you’d like to collect. Depending on which part of Jenkins you monitor, you’ll need to specify different loggers. Tell us the symptom of your problem in the users list and we should be able to tell you where you need to look. Also, this is really just a wrapper around the java.util.logging package, so if you program in Java, you might be able to guess where to look.
Once the set up is complete, Jenkins will start collecting data. The collected logs are available from the web UI.
The simplest solution is to install the Support Core Plugin, which causes custom logs to be written to disk automatically.
Create a file
logging.properties in which you define the logging
levels and a
ConsoleHandler Then pass this file to the JVM by adding
the system property
In the logging.properties file please add the below line: