⛏️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 Parsing Forge • Room 3

SPL Lab: Auditing Forwarder Connections

When events stop arriving in Splunk Cloud or parsing issues appear, start by auditing forwarder telemetry in the _internal index.

Every forwarder connecting over TCP 9997 logs periodic metrics to metrics.log under group=tcpin_connections, exposing hostname, sourceIp, fwdType (uf vs full), and event throughput.

Practice writing an SPL search against _internal to find the latest check-in timestamp for each connected forwarder hostname and sourceIp.

Example forwarder telemetry query in _internal
index=_internal source=*metrics.log group=tcpin_connections
| stats latest(_time) as last_seen, values(fwdType) as type by hostname, sourceIp
| convert ctime(last_seen)
Filtering on source=*metrics.log group=tcpin_connections before piping to stats keeps _internal diagnostic searches fast and low-SVC.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
Write an SPL query in _internal (source=*metrics.log group=tcpin_connections) that computes the latest(_time) as last_seen grouped by hostname and sourceIp.
Splunk Search Bar
>