Commit | Line | Data |
---|---|---|
727aa690 PP |
1 | --- |
2 | id: whats-new | |
3 | --- | |
4 | ||
5 | Most of the changes of LTTng 2.6 are bug fixes, making the toolchain | |
6 | more stable than ever before. Still, LTTng 2.6 adds some interesting | |
7 | features. | |
8 | ||
9 | LTTng 2.5 already supported the instrumentation and tracing of | |
10 | [Java applications](#doc-java-application) through `java.util.logging` | |
11 | (JUL). LTTng 2.6 goes one step further by supporting | |
12 | <a href="https://logging.apache.org/log4j/1.2/" class="ext">Apache log4j 1.2</a>. | |
13 | The new log4j domain is selected using the `--log4j` option in various | |
14 | commands of the `lttng` tool. | |
15 | ||
16 | LTTng-modules has supported system call tracing for a long time, | |
17 | but until now, it was only possible to record either all of them, | |
18 | or none of them. LTTng 2.6 allows the user to record only a specific | |
19 | subset of system call events, e.g.: | |
20 | ||
21 | <pre class="term"> | |
22 | lttng enable-event --kernel --syscall open,fork,chdir,pipe | |
23 | </pre> | |
24 | ||
25 | Finally, the `lttng` command line tool cannot only communicate with | |
26 | humans as it used to do, but also with machines thanks to its new | |
27 | [machine interface](#doc-mi) feature. | |
26418fc3 PP |
28 | |
29 | To learn more about the new features of LTTng 2.6, see | |
30 | [this release announcement](//lttng.org/blog/2015/02/27/lttng-2.6-released/). |