- /*
- * From this point on, the above message will be collected in the trace
- * if the event "Hello" is enabled for the JUL domain using the lttng
- * command line or the lttng-ctl API. For instance:
- *
- * $ lttng enable-event -j Hello
- */
-
- /*
- * A new logger is created here and fired after. Typically with JUL, you
- * use one static Logger per class. This example here can represent a
- * class being lazy-loaded later in the execution of the application.
- *
- * The agent has an internal timer that is fired every 5 seconds in
- * order to enable events that were not found at first but might need to
- * be enabled when a new Logger appears. Unfortunately, there is no way
- * right now to get notified of that so we have to actively poll.
- *
- * Using the --all command for instance, it will make this Logger
- * available in a LTTng trace after the internal agent's timer is fired.
- * (lttng enable-event -j -a).
- */
- Logger helloLogDelayed = Logger.getLogger("hello_delay");
-
- /*
- * Attach a handler to this new logger.
- *
- * Using the same handler as before would also work.
- */
- Handler lttngHandler2 = new LttngLogHandler();
- helloLogDelayed.addHandler(lttngHandler2);
-
- System.out.println("Firing hello delay in 10 seconds...");
- Thread.sleep(10000);
- helloLogDelayed.info("Hello World delayed...");
-
- System.out.println("Cleaning Hello");
-
- /*
- * Do not forget to close() all handlers so that the agent can shutdown
- * and the session daemon socket gets cleaned up explicitly.
- */