Determine your Splunk Cloud Platform Experience

Your Splunk Cloud Platform deployment has one of two possible Experience designations: Classic or Victoria. For information on the differing capabilities of each Splunk Cloud Platform Experience, see Differences between Classic Experience and Victoria Experience.

To determine your Splunk Cloud Platform Experience:

1. In Splunk Web, click Support & Services > About.
2. In the About panel, under Splunk Cloud, find your Experience: Classic or Victoria.

Differences between Classic Experience and Victoria Experience

Classic Experience and Victoria Experience provide nearly identical capabilities, with the following exceptions:

• Self-service app installation: Splunk Cloud Platform deployments on Victoria Experience support self-service app installation of private apps and most public apps available on Splunkbase. For more information on self-service app installation, see Install apps on your Splunk Cloud Platform deployment.

When you install an app using self-service app installation on Victoria Experience, the app is automatically installed on all search heads and search head cluster members across your deployment, including premium search heads running premium apps, such as Splunk IT Service Intelligence (ITSI) and Splunk Enterprise Security (ES).

• Inputs Data Manager (IDM): Splunk Cloud Platform deployments on Victoria Experience do not require an IDM. You can now run modular and scripted inputs directly on a Victoria Experience search head without the overhead of a separate IDM instance. Upon upgrade from Classic Experience to Victoria Experience, Splunk migrates all apps, customizations, and configs from the IDM to the primary search head or search head cluster, and removes the IDM from your deployment. Note that users with sc_admin and apps roles can see all configurations on the search tier, including the newly migrated apps from the IDM. For more information on IDM, see Splunk Cloud Platform features.

If your IDM requires special IP allowlisting, you must move that allowlisting to the search head IP address, as all inputs now run on the search tier. If your search tier is a search head cluster, you must include all SHC member IP addresses in the allowlist.

• Hybrid Search: Splunk Cloud Platform deployments on Victoria Experience do not support hybrid search. If your deployment is on Victoria Experience, you must use federated search instead. For more information on federated search, see Migrate from hybrid search to federated search in the Splunk Cloud Search Manual.

• HTTP Event Collector (HEC): Splunk Cloud Platform deployments on Victoria Experience support HEC token management using Splunk Web and Admin Configuration Service (ACS) endpoints. Deployments on Classic Experience support HEC token management using Splunk Web and Splunk Cloud Classic endpoints. For more information on using ACS and Splunk Cloud Classic endpoints for HEC token management, see Manage HEC tokens in Splunk Cloud Platform.

For more information on the differences between Classic Experience and Victoria Experience, see Experience designations in the Splunk Cloud Platform Service Description.

Splunk assigns your deployment to an appropriate Splunk Cloud Platform Experience for you. You cannot independently change your current Experience. For further details, contact your Splunk Cloud Platform representative.