In this example, after a successful download a HEAD request will be issued to:

In this example, after a successful download a HEAD request will be issued to:

−

http://arthorne.com/bogusstats/test.plugin.1.bundle

+

http://your.stats.server/stats/test.plugin.1.bundle

−

(value of the "downloads.stats" property appended to the value of the

+

(value of the '''downloads.stats''' property appended to the value of the

−

"p2.statsURI").

+

'''p2.statsURI''').

+

+

You can either install software on the server at that location to count the requests, or simply gather the statistics from your web server log files.

+

+

= Customized stats based on the repository that is stats available =

+

+

Application providers might want to stats the detail download stats, such as the name of distribution package, distribution version and the information of host os. The release engineers of applications can initialize the customized downloading stats data when building release version.

+

+

The value of customized stats should be set in the default profile of the distrubited applications. See [http://help.eclipse.org/indigo/topic/org.eclipse.platform.doc.isv/guide/p2_director.html P2 Director] for how to specify profile property when materializing your application.

+

+

For example, the customized downloading stats is below in the p2 profile of Juno's J2EE windows package,

Revision as of 02:00, 25 January 2012

Contents

Overview

p2 includes a rudimentary mechanism for obtaining download statistics to track transfers from an artifact repository. This page describes how to enable statistics gathering for artifacts in your p2 repositories.

The p2 download statistics mechanism has the following characteristics:

Statistics collection is "best effort": transfers do not fail if stats could not be collected

Each artifact repository controls how and where statistics are collected for transfers from

that repository. If artifact repository A is gathering statistics, and an artifact is transferred from repository A to B, and then from repository B to C, repository A will only obtain statistics for the transfer from A to B.

No personal information is collected. Essentially the statistics just summarize the transfers that have occurred from that repository.

The repository maintainer can control the granularity of statistics gathered. For example they can record every single artifact transfer, or only transfers of particular artifacts. In general it is best to minimize the set of artifacts that are tracked, since each artifact transfer that is recorded incurs an extra round trip from the client to the repository.

Enabling stats in your repository

There are two steps to enable p2 download statistics gathering for your repository:

1) In the artifact repository that you want to track downloads from, add a
p2.statsURI property specifying the statistics URL (in artifacts.jar):

(value of the downloads.stats property appended to the value of the
p2.statsURI).

You can either install software on the server at that location to count the requests, or simply gather the statistics from your web server log files.

Customized stats based on the repository that is stats available

Application providers might want to stats the detail download stats, such as the name of distribution package, distribution version and the information of host os. The release engineers of applications can initialize the customized downloading stats data when building release version.

The value of customized stats should be set in the default profile of the distrubited applications. See P2 Director for how to specify profile property when materializing your application.

For example, the customized downloading stats is below in the p2 profile of Juno's J2EE windows package,