Linux Trace terminology - feedback requested

[Tim Bird <tim dot bird at am dot sony dot com>]

Hi all,  please forgive the massive cross-post.

I'm working on coordinating some collaboration between some of the major
tracing systems in Linux, and as a first step I'm working on some terminology
definitions.  This is just to see what people call different things, and is a
precursor to putting together a taxonomy of features and attributes for the
different tracers.

Here is my first attempt:

 * event - an instruction location or system state at a specific point in time
 * event data - information related to an event
    * ie. In some trace systesm, event data size can vary depending on the event.
 * capture - the act of recording event information
 * trace point - a location in the traced software, where an event is "emitted"
 * trace buffer - location where trace data is stored at time of capture
 * trace log - location where trace data is stored long-term
 * configuration interface - the API or mechanism used to configure the tracing engine
 * control interface - the API or mechanism used to control the tracing engine
 * transfer interface - the API or mechanism used to move the trace data from
   kernel to user space
 * trace time - the time when the trace is active
    * ie The trace buffer may be accessed at trace time, that is, while the trace is active.
 * post-processing - manipulation of the trace data after the trace is collected
 * configuration - the set of constraints which determine what events are collected
   and how they are processed in a trace
 * static tracepoint - a trace point statically compiled into the software being traced
 * dynamic tracepoint - a trace point dynamically added to the software being traced
 * aggregation - updating statistics or other analytical information, based on trace events
     * ie. SystemTap can do aggregation at trace time, while KFT and LTTng do
       aggregation during post-processing (mostly).
 * filters - criteria used to limit the events that are processed or captured
 * triggers - criteria used to start and stop tracing automatically

Does your tracing system use different terms for any of the above?
If so, what are they?

Are there any other important terms I am missing?

Your feedback is really appreciated.

Thanks,
 -- Tim

P.S. Nojiri-san - sorry, but I didn't know what list to send to to get
feedback from LKST people.  The english sourceforge list for LKST seems defunct.
Can you forward this as appropriate?  Thanks.

=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Electronics
=============================