Feature #211

Environment vars

Added by Matthew Khouzam almost 9 years ago. Updated almost 5 years ago.

Target version:
Start date:
Due date:
04/12/2013 (over 7 years late)
% Done:


Estimated time:


Hi, I think it would be an interesting items to put in the environment variables.
  • Session creation time. ( To be sure you're dealing with the right trace)
  • Session destruction time.
  • Cpuinfo ( to understand performance, if you're running a 386 or an i7, the latencies are different)
  • Amount of Ram ( could quickly explain swapping)
  • hw info
  • network info
  • hostname (oops tracing the wrong machine)

Updated by Anonymous almost 9 years ago

  • Project changed from Website to LTTng

Updated by Yannick Brosseau over 8 years ago

Matthew, that's for the kernel tracer right?


Updated by Mathieu Desnoyers over 8 years ago

That would be for both userspace and kernel tracing. All this extra
information would have to be gathered by lttng-sessiond, since this is
the "one place" that we know has access to things like /proc/cpuinfo,
the hostname, etc etc. (e.g. the kernel tracer does not have easy
access to this information, if we consider setups with containers). The
sessiond would then have to send that information to the tracers when
ust or kernel tracing sessions are created (we are planning to add a
"set attribute" on the session for that kind of purpose, so we might as
well create a set attribute at the kernel/ust session level.


Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.


Updated by Jonathan Rajotte Julien almost 5 years ago

  • Target version set to Wishlist

Also available in: Atom PDF