Eclipse is probably best known as a Java IDE, but it is more: it is an IDE framework, a tools framework, an open source project, a community, an eco-system, and a foundation.

This page is deprecated and may contain some information that is no longer relevant or accurate.

UDC Technical FAQ

This FAQ is concerned with questions of technical nature. Questions concerning the capture and use of the data by The Eclipse Foundation can be found UDC Data Capture and Use FAQ.

What releases of Eclipse does the Usage Data Collector support?

The Usage Data Collector can be installed into the Europa (Eclipse Top Level Project SDK 3.3.x) or Ganymede (Eclipse Top Level Project SDK 3.4.x) Eclipse releases and milestone builds.

How do I install the Usage Data Collector?

The Usage Data Collector is included as part of the "UDC" packages produced by the EPP. An automated build process generates a new build that can be installed into Eclipse by pointing the update manager to:

For more information about the build process and status, please see Bug 215060.

How do I get the code?

If you want to load the code as projects into your workspace, it is available in the Technology Project's CVS repository. Use this Team Project Set to add the Usage Data Monitor to your workspace.

You can also browse the code online.

How do I turn off the Usage Data Collector?

There is an option on the "Usage Data Collection" preferences page labeled "Enable Capture". Turn this option off.

Where is the information stored?

As the usage data is collected, it is stored locally in the ./.metadata/.plugins/org.eclipse.epp.usagedata.recording directory of the Eclipse workspace. After data has been successfully uploaded and the data has been transferred into the Eclipse Foundation's database, the local files are deleted.

What information is captured?

The UDC captures the the following information:

  1. Bundles (also known as plug-ins) that are started by the system.
  2. Commands accessed via keyboard shortcuts, and actions invoked via menus or toolbars.
  3. Perspective changes
  4. View and editor open, close, and activation events (activations occur when a view or editor is given focus).
  5. System information, such as JVM name and version, operating system, and window system (new with version 1.1.0).
  6. The description of internal errors (exceptions logged with a severity of "ERROR").

For each item captured, we also capture the idenfier and version of the bundle that contributes the item. When information is uploaded, we further capture the country from which the upload originated.

It's valuable to also note what we do not capture. We do not capture any personal information. We do not capture IP addresses. We do not capture any information that will allows us to identify the source of the information.

Two different keys are used to identify the source of the uploaded data. The first key identifies the workstation; this key is stored locally in your "user home" directory. The second key identifies the workspace; this key is stored in the ./.metadata/.plugins/org.eclipse.epp.usagedata.recording directory for the workspace. These keys are uploaded along with the usage data. These keys allow us to correlate data.

How do we change the upload target?

The server to which the UDC uploads data can be configured using the org.eclipse.epp.usagedata.recording.upload-url system property. This property can be set either on the command-line for Eclipse, or in the eclipse.ini file. For example:


Note that "-D" parameters should follow "-vmargs" on the command-line.

More information

The following pages are hosted by The Eclipse Foundation