[lttng-docs.git] / contents / using-lttng / instrumenting / java-application / intro.md

---
id: java-application
---

LTTng-UST provides a _logging_ back-end for Java applications using
either
<a href="http://docs.oracle.com/javase/7/docs/api/java/util/logging/Logger.html" class="ext"><code>java.util.logging</code></a>
(JUL) or
<a href="http://logging.apache.org/log4j/1.2/" class="ext">Apache log4j 1.2</a>.
This back-end is called the _LTTng-UST Java agent_, and it is responsible
for the communications with an LTTng session daemon.

From the user's point of view, once the LTTng-UST Java agent has been
initialized, JUL and log4j loggers may be created and used as usual.
The agent adds its own handler to the _root logger_, so that all
loggers may generate LTTng events with no effort.

Common JUL/log4j features are supported using the `lttng` tool
(see [Controlling tracing](#doc-controlling-tracing)):

  * listing all logger names
  * enabling/disabling events per logger name
  * JUL/log4j log levels
Commit	Line	Data
215610eb PP	1	---
	2	id: java-application
	3	---
	4
	5	LTTng-UST provides a _logging_ back-end for Java applications using
	6	either
	7	<a href="http://docs.oracle.com/javase/7/docs/api/java/util/logging/Logger.html" class="ext"><code>java.util.logging</code></a>
	8	(JUL) or
	9	<a href="http://logging.apache.org/log4j/1.2/" class="ext">Apache log4j 1.2</a>.
	10	This back-end is called the _LTTng-UST Java agent_, and it is responsible
	11	for the communications with an LTTng session daemon.
	12
	13	From the user's point of view, once the LTTng-UST Java agent has been
	14	initialized, JUL and log4j loggers may be created and used as usual.
	15	The agent adds its own handler to the _root logger_, so that all
	16	loggers may generate LTTng events with no effort.
	17
	18	Common JUL/log4j features are supported using the `lttng` tool
	19	(see [Controlling tracing](#doc-controlling-tracing)):
	20
	21	* listing all logger names
	22	* enabling/disabling events per logger name
	23	* JUL/log4j log levels