projects / babeltrace.git / blame
| Commit | Line | Data |
|---|---|---|
| c00617c9 JD |
1 | LTTNG LIVE |
| 2 | ---------- | |
| 3 | ||
| 4 | This is a brief howto for using the Babeltrace with LTTng live protocol. | |
| 5 | LTTng live allows the user to read a trace while it is running. | |
| 6 | ||
| 7 | In order to create a live LTTng session, please refer to the LTTng | |
| 8 | documentation (version >= 2.4). | |
| 9 | ||
| 10 | Once the session is created and Babeltrace is installed, you can list the | |
| 11 | sessions with : | |
| 12 | $ babeltrace -i lttng-live net://<your-relayd-hostname> | |
| 13 | ||
| 14 | The output should look like this : | |
| 15 | net://localhost/host/myhostname/mysessionname (timer = 1000000, 5 stream(s), 0 client(s) connected) | |
| 16 | ||
| 17 | It means that the session mysessionname on the host myhostname is currently | |
| 18 | streaming its data to the relayd on localhost. | |
| 19 | ||
| 20 | To attach to this session and start receiving the trace : | |
| 21 | $ babeltrace -i lttng-live net://localhost/host/myhostname/mysessionname | |
| 22 | ||
| 23 | You should now see trace data flowing in your console when events are produced. | |
| 24 | ||
| 25 | To report bugs, please use the same procedure as reporting bugs to Babeltrace, | |
| 26 | but don't forget to add the -v to the commands above to provide enough debug | |
| 27 | information. |