Java Usage Tracker & Telemetry

About Java Usage Tracker

The Java Usage Tracker is a feature that enables organizations and Oracle to better understand how the Java Runtime Environment is being used. When enabled, the Usage Tracker records information about JRE usage and sends periodic reports to a configured endpoint.

This data helps Oracle improve the Java platform, identify compatibility issues, and deliver more relevant security patches. Usage tracking is optional and can be configured at the system or enterprise level.

Note: Usage Tracker was introduced in Java SE 8 Update 77. Enterprise administrators can manage tracking centrally through the Java Control Panel or via enterprise group policy.

Telemetry Preferences

Configure which categories of data the Java Runtime may collect and report. Changes take effect after the next JVM restart.

Basic JVM Information

JRE version, vendor, JVM name, and runtime arguments

Operating System Details

OS name, version, architecture, locale, and timezone

Heap & Memory Usage

Initial/max heap size, metaspace usage, GC statistics

Class Loading Statistics

Number of classes loaded/unloaded, classloader hierarchy

Thread & CPU Metrics

Thread counts, CPU time, peak thread usage

Network Configuration

Proxy settings, TLS versions, cipher suites in use

Crash & Error Reporting

JVM crash logs, OutOfMemoryError events, fatal error data

Data Categories Reference

Category	Data Points	Frequency
JVM Identity	java.version, java.vm.name, java.vm.vendor, java.runtime.version	Per session
Operating System	os.name, os.version, os.arch, user.language, user.timezone	Per session
Heap Usage	Initial heap (-Xms), max heap (-Xmx), used heap, free heap, GC type	Every 15 min
Class Loading	Loaded class count, unloaded class count, total loaded since start	Every 15 min
Thread Info	Live thread count, daemon thread count, peak thread count	Every 15 min
Network	Proxy host (hashed), TLS protocol version, enabled cipher suites	Per session
Error Data	hs_err log contents (anonymized), heap dump metadata, error codes	On event

Enterprise Configuration (Legacy)

System administrators can also configure the legacy Java Usage Tracker through the Java Control Panel or via enterprise group policy. The Usage Tracker can be configured to log usage data locally, report to a centralized endpoint, or be disabled entirely based on organizational requirements.

Enterprise Tip: Use your organization's configuration management tools (such as Group Policy, SCCM, or Intune) to deploy consistent telemetry settings across all managed endpoints in your Java estate.

Privacy Notice

Oracle collects Java usage data in accordance with the Oracle Privacy Policy. Telemetry data is transmitted over encrypted HTTPS connections and stored on Oracle infrastructure within the United States and European Union. Data is retained for a maximum of 36 months and is used solely for product improvement, security analysis, and license compliance purposes.

No personally identifiable information (PII) is intentionally collected through the Usage Tracker. However, certain system properties (such as user.home or user.name) are excluded by default to protect user privacy. Oracle does not sell telemetry data to third parties.

For questions about Java telemetry, contact Oracle Privacy Office or refer to the full Privacy Policy.