⛏️GetSplunky!
Lv.1Intern
0 XP
0
Home Map Stats Drill Board Log In
CoursesArticlesSPL Cheat SheetCertification PathAboutPrivacyTerms

Splunky is an independent, free study resource. It is not affiliated with, endorsed by, or sponsored by Splunk or Cisco. Splunk, SPL and related marks are trademarks of Splunk, a Cisco company, and are used here only to identify the certifications this site helps you study for.

© 2026 Splunky

Back to Floor
The Cloud Citadel • Room 1

Victoria Experience vs. Classic Experience

Splunk Cloud Platform operates in two architectural generations: the legacy Classic Experience and the modern Victoria Experience. Understanding which experience your stack runs determines where apps install, how index-time configurations propagate, and whether an Inputs Data Manager (IDM) exists.

In the Victoria Experience, Splunk eliminates the separate IDM node and executes modular and scripted inputs directly on the Search Head or Search Head Cluster (SHC) tier. When you install an app via Self-Service App Install (SSAI) or the Admin Config Service (ACS) API on Victoria, Splunk automatically distributes it across all search heads (including premium stacks) and pushes index-time configurations such as props.conf, transforms.conf, and indexes.conf to the indexer tier.

In the Classic Experience, modular and scripted inputs run on a dedicated managed IDM tier rather than on the search heads, and app deployments or index-time configuration updates frequently require Splunk Support tickets or separate tier coordination. Additionally, Victoria restricts downloading previously uploaded apps back out of the Splunk Web UI.

Classic vs. Victoria app endpoints (ACS API v2)
# Victoria Experience app installation
POST https://admin.splunk.com/{stack}/adminconfig/v2/apps/victoria

# Classic Experience app installation
POST https://admin.splunk.com/{stack}/adminconfig/v2/apps
When a stack upgrades from Classic to Victoria Experience, Splunk automatically migrates IDM apps and inputs to the Search Head tier and decommissions the IDM.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Drag items to their correct zone (or tap item then tap zone on mobile)
Modular and scripted inputs run directly on the Search Head tier without an IDM
Requires a separate managed Inputs Data Manager (IDM) for cloud-hosted scripted inputs
SSAI automatically pushes index-time props.conf and transforms.conf to indexers
Supports downloading previously uploaded apps via Splunk Web UI and uses /adminconfig/v2/apps
Victoria Experience
Classic Experience