Project

General

Profile

Actions
Copy link

Feature #211

open

Environment vars

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

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Wishlist
Start date:
04/12/2012
Due date:
04/12/2013 (over 8 years late)
% Done:

0%

Estimated time:

Description

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)
Actions
Copy link
 #1

Updated by Anonymous about 9 years ago

  • Project changed from Website to LTTng
Actions
Copy link
 #2

Updated by Yannick Brosseau almost 9 years ago

Matthew, that's for the kernel tracer right?

Actions
Copy link
 #3

Updated by Mathieu Desnoyers almost 9 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

--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

Actions
Copy link
 #4

Updated by Jonathan Rajotte Julien about 5 years ago

  • Target version set to Wishlist
Actions
Copy link

Also available in: Atom PDF