Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
id: lttng-live
+since: 2.4
---
We have seen how trace files may be produced by LTTng out of generated
---
id: mi
+since: 2.6
---
The `lttng` tool aims at providing a command output as human-readable as
---
id: saving-loading-tracing-session
+since: 2.5
---
Configuring a tracing session may be long: creating and enabling
---
id: taking-a-snapshot
+since: 2.3
---
The normal behavior of LTTng is to record trace data as trace files.
---
id: tracef
+since: 2.5
---
`tracef()` is a small LTTng-UST API to avoid defining your own
---
id: java-application
+since: 2.4
---
LTTng-UST provides a _logging_ back-end for Java applications using
---
id: jul
+since: 2.4
---
Here's an example of tracing a Java application which is using
---
id: liblttng‑ust‑dl
+since: 2.4
---
This LTTng-UST helper causes all calls to `dlopen()` and `dlclose()`
---
id: liblttng‑ust‑libc‑pthread-wrapper
+since: 2.3
---
`liblttng-ust-libc-wrapper.so` and `liblttng-ust-pthread-wrapper.so`
---
id: proc-lttng-logger-abi
+since: 2.5
---
The `lttng-tracer` Linux kernel module, installed by the LTTng-modules