[ https://issues.jboss.org/browse/JBIDE-14016?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14016: ------------------------------------ 1. Platform specific bits, as I said above, will be obvious from the feature, if the feature is platform-specific. If not, then there's nothing we can do. 2. "Can we see the OS in the useragent in the stats" - no, unless you throw a patch at Eclipse.org and get them to apply it. 3. The installer process creates an update site including these markers attached to the features' metadata. Since the features are not platform specific, there's no os= value to set. Remember all we're tracking are DOWNLOADS, not INSTALLS. So when the izpack process fires on a given machine to install the features, all it's doing is downloading from a local zip, & pinging the server to track the HTTP HEAD requests. There's no step in the install process where the update site metadata can be REBUILT on the fly to insert OS details. 4. Package and version are obvious from the tracker URL, eg, for the JBDS product feature you'd see a hit for this: {code}http://download.jboss.org/jbosstools/usage/installs/${JOB_NAME}/${project.version}/${BUILD_ALIAS}/${buildQualifier}/com.jboss.jbds.product.feature_7.0.0.Alpha2-v20130412-1701-B142{code} So for features in both JBT and JBDS, you can differentiate using JOB_NAME: if it contains "devstudio" will be from a JBDS site rather than a JBT site. Adding querystring values IMHO is no different from adding path segments. It's just a different thing to look at when parsing the HTTP HEAD logs into useful data. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira