About update checker data
A small amount of information about your Splunk Enterprise version and platform is sent to Splunk. Splunk uses the data to understand the number of customers using older versions of Splunk Enterprise and Splunk apps. Your Splunk software instance uses the data to display a message in Splunk Web when a new version is available.
Two types of update checker data are sent, Enterprise update checker data and app update checker data.
For more information about the data that your deployment can send to Splunk, see Share data in Splunk Enterprise.
Enterprise update checker data
Sample Enterprise update checker data
The following types of data are sent for Splunk Enterprise.
|License group, subgroup, and hashed GUID||Enterprise, Production, <GUID>|
|Splunk software version||7.0.0|
App update checker data
Update checker data about your Splunk apps is sent to Splunk daily via a REST call from splunkd to splunkbase.splunk.com. This data is correlated with information about app downloads to populate the app analytics views on Splunkbase for an app's developer, and to compute the number of installs on the app details page.
You can turn off update checker reporting for a Splunk app in app.conf in the app directory. Set the
check_for_updates setting to
Sample app update checker data
The following types of data are sent on a per-app basis.
|App ID, name, and version||gettingstarted, Getting Started, 1.0|
|Platform, architecture||Darwin, x86_64|
Share data in Splunk Enterprise
How Splunk Enterprise licensing works
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.3.0, 7.3.1