Skip to main content
Jump to: navigation, search

UDC/What Gets Captured

Revision as of 14:04, 22 September 2010 by (Talk | contribs)

At a high-level, the Usage Data Collector (UDC) monitors what is being used and when (timestamp), including:

  • Runtime environment (operating system, host Java runtime, etc.)
  • Bundles
  • Commands accessed via keyboard shortcuts
  • Actions invoked via menus or toolbars
  • Perspective changes
  • View usage
  • Editor usage

The UDC uses a collection of "monitors" to gather information. These monitors are started when the UDC starts up; generally, they install observer hooks into the Eclipse framework.

Each usage data event is stored in a table that is transmitted to the Eclipse Foundation Server. Files are in CSV-format with the following columns:

  • what - What happened (i.e. the event), e.g. "activated", "started", "executed", ...
  • kind - The kind of thing that caused the event (i.e. the source), e.g. "view", "editor", "command", ...
  • bundleId - The name of the bundle that "owns" the thing that caused the event, e.g. "org.eclipse.ui.editors"
  • bundleVersion - The version of the bundle, e.g. "3.6.0.v20100520-0800"
  • description - Event-specific information, e.g. "org.eclipse.pde.ui.PDEPerspective"
  • time - Time of the event (millisecond clock value from the workstation)

FWIW, we recognized (too late) that what and kind are terrible names for what should probably be called event and source.

Runtime Environment

Every time Eclipse is started, the runtime environment is recorded by the UDC. This functionality is implemented by This monitor does not install any hooks, it just grabs system information. Since this monitor gathers information every time Eclipse is started, the information that it gathers may be somewhat redundant. However, it should indicate changes in the runtime environment over time.

For all runtime environment "events", the kind is "sysinfo", what is the name of a property (see below), and description contains the value of the corresponding system property. No bundle id or version is captured.

Properties Captured

  • os - The operating system (result of calling Platform.getOS()), e.g. "linux";
  • arch - The system architecture (result of calling Platform.getOSArch()), e.g. "x86"
  • ws - The windowing system (result of calling Platform.getWS()), e.g. "gtk"
  • locale - Locale (result of calling Platform.getNL()), e.g. "en_CA"
  • processors - Number of available processors, e.g. "2"
  • System properties (result of calling System.getProperty(name))
    •, e.g. "Java(TM) SE Runtime Environment"
    • java.runtime.version, e.g. "1.6.0_14-b08"
    •, e.g. "Java Platform API Specification"
    • java.specification.vendor, e.g. "Sun Microsystems Inc."
    • java.specification.version, e.g. "1.6"
    • java.vendor, e.g. "Sun Microsystems Inc."
    • java.version, e.g. "1.6.0_14"
    • java.vm, e.g. "mixed mode, sharing"
    •, e.g. "Java HotSpot(TM) Client VM"
    •, e.g. "Java Virtual Machine Specification"
    • java.vm.specification.vendor, e.g. "Sun Microsystems Inc."
    • java.vm.specification.version, e.g. "1.0"
    • java.vm.vendor, e.g. "Sun Microsystems Inc."
    • java.vm.version, e.g. "14.0-b16"


processors,sysinfo,,,"2",1282863531114,sysinfo,,,"Java(TM) SE Runtime Environment",1282863531114
java.runtime.version,sysinfo,,,"1.6.0_14-b08",1282863531114,sysinfo,,,"Java Platform API Specification",1282863531114
java.specification.vendor,sysinfo,,,"Sun Microsystems Inc.",1282863531114
java.vendor,sysinfo,,,"Sun Microsystems Inc.",1282863531114
java.version,sysinfo,,,"1.6.0_14",1282863531114,sysinfo,,,"mixed mode, sharing",1282863531114,sysinfo,,,"Java HotSpot(TM) Client VM",1282863531114,sysinfo,,,"Java Virtual Machine Specification",1282863531114
java.vm.specification.vendor,sysinfo,,,"Sun Microsystems Inc.",1282863531114
java.vm.vendor,sysinfo,,,"Sun Microsystems Inc.",1282863531114


Bundle usage information is captured by

This monitor installs a listener on the bundle context; it records all reported bundle-specific events. Since we have little control over the order in which our bundle starts, the first thing that this monitor does is get a list of all bundles that have previously been started and reports "started" events for each of them.

For each bundle "event", the kind is "bundle", what is the event (e.g. "started"; see below), and description is the symbolic name of the bundle. The bundle id and bundle version are also captured.

Bundle Events

  • "unknown";
  • "updated";
  • "unresolved";
  • "uninstalled";
  • "stopping";
  • "stopped";
  • "starting";
  • "resolved";
  • "lazy_activation";
  • "installed";
  • "started"



Back to the top