⛏️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 Ingest Gateway • Room 3

IDM, Heavy Forwarders & Data Manager

Selecting the right ingestion tier depends on both your Splunk Cloud experience and the data source type. In Classic Experience, cloud-hosted API polling and scripted inputs run on the Inputs Data Manager (IDM), whereas Victoria Experience removes the IDM and runs those modular inputs directly on the Search Head tier.

Customer-managed Heavy Forwarders (HFs) remain essential whenever you need on-premises network listeners (such as syslog via SC4S or TCP/UDP inputs), Splunk DB Connect against private databases, or heavy pre-ingest filtering and masking before traffic leaves your network.

For cloud-native telemetry from AWS, Azure, or GCP, Splunk Data Manager provides a guided, zero-forwarder automation workflow that provisions cloud-provider pipelines (such as Kinesis Firehose, Event Hubs, or Pub/Sub) into Splunk Cloud HEC.

Choosing the right collection tier
# File/Windows logs on endpoints -> Universal Forwarder + splunkclouduf.spl
# Private DB Connect / Syslog / Local Masking -> On-prem Heavy Forwarder
# Cloud SaaS / API polling -> Victoria Search Tier (or Classic IDM)
# Native AWS/Azure/GCP account telemetry -> Splunk Data Manager (HEC)
Splunk Cloud indexers never open arbitrary TCP/UDP syslog ports to the internet; always terminate syslog on an on-prem Heavy Forwarder or SC4S and forward over S2S 9997 or HEC 443.

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)
Lightweight endpoint agent tailing local /var/log files with minimal footprint
On-premises Splunk DB Connect queries and local syslog/SC4S pre-filtering
Runs cloud-hosted modular and scripted inputs natively without a Classic IDM node
Automated native AWS, Azure, and GCP telemetry onboarding over HEC
Universal Forwarder
Heavy Forwarder
Victoria Search Tier (ex-IDM)
Data Manager