From 024571e4a2dd69dfb60866f46cb01f38a50b4734 Mon Sep 17 00:00:00 2001
From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Fri, 4 Sep 2015 20:20:59 -0400
Subject: [PATCH] Document Python application logging

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
 .../instrumenting/python-application.md       | 67 +++++++++++++++++++
 toc/docs.yml                                  |  2 +
 2 files changed, 69 insertions(+)
 create mode 100644 contents/using-lttng/instrumenting/python-application.md

diff --git a/contents/using-lttng/instrumenting/python-application.md b/contents/using-lttng/instrumenting/python-application.md
new file mode 100644
index 0000000..d3ca711
--- /dev/null
+++ b/contents/using-lttng/instrumenting/python-application.md
@@ -0,0 +1,67 @@
+---
+id: python-application
+since: 2.7
+---
+
+Python 2 and Python 3 applications using the standard
+<a href="https://docs.python.org/3/howto/logging.html" class="ext"><code>logging</code> module</a>
+can be traced by LTTng using the LTTng-UST Python agent.
+
+Import the `lttngust` package in your Python application. For example:
+
+~~~ python
+import lttngust
+import logging
+
+
+def example():
+    logger = logging.getLogger('my-logger')
+
+    while True:
+        logger.debug('debug message')
+        logger.info('info message')
+        logger.warn('warn message')
+        logger.error('error message')
+        logger.critical('critical message')
+        time.sleep(1)
+
+
+if __name__ == '__main__':
+    example()
+~~~
+
+Importing `lttngust` adds a logging handler which emits LTTng-UST
+events. You do not need to get a special logger for tracing to work.
+
+Use the `--python` option of the `lttng enable-event`,
+`lttng disable-event`, and `lttng list` commands to target
+Python applications. For example, here's how to enable the events
+produced by the Python logger above:
+
+<pre class="term">
+lttng enable-event --python my-logger
+</pre>
+
+Standard Python log levels are supported using the `PYTHON_` prefix.
+For example, here's how to enable the warning (and more important)
+events produced by the Python logger above:
+
+<pre class="term">
+lttng enable-event --python my-logger --loglevel PYTHON_WARNING
+</pre>
+
+See [Enabling and disabling events](#doc-enabling-disabling-events) for
+more options.
+
+When loading, the LTTng-UST Python agent tries to register to the
+[session daemon](#doc-lttng-sessiond). Note that the session daemon
+needs to be started _before_ the Python application is started. If a
+session daemon is found, the agent tries to register to it during
+5&nbsp;seconds, after which the application continues without LTTng
+tracing support. This timeout value is overriden by the
+`LTTNG_UST_PYTHON_REGISTER_TIMEOUT` environment variable (milliseconds).
+
+If the session daemon stops while a registered Python application is
+registered, the application retries to connect and register to a session
+daemon every 3&nbsp;seconds. This timeout value is overridden by the
+`LTTNG_UST_PYTHON_REGISTER_RETRY_DELAY` environment variable.
diff --git a/toc/docs.yml b/toc/docs.yml
index 59c0b7c..9fa03ea 100644
--- a/toc/docs.yml
+++ b/toc/docs.yml
@@ -146,6 +146,8 @@ cats:
                 title: <code>java.util.logging</code>
               - id: log4j
                 title: Apache log4j 1.2
+          - id: python-application
+            title: Python application
           - id: instrumenting-linux-kernel
             title: Linux kernel
             cats:
-- 
2.34.1