Splunk Linux Use Case

Blame It on the Network (Prove It)

3am "the app is slow" - who is lying?

The scenario

"The app is slow." The developer blames the network; the network person blames the app; the database blames everyone. Meanwhile the truth is one of: NIC link retraining to half-duplex at midnight, an interface dropping 3 % of packets, IO stall from a noisy neighbor, or OOM swap-thrash. Every one of those has telemetry - you just have to have the four apps that read it.

The app recipe

TA-netqual Per-interface operstate, carrier/speed, rx/tx errors + drops, link-flap events
TA-psi Pressure Stall Information: is CPU/memory/IO actually stalling tasks
TA-memwatch Free memory, swap-in activity (the signature of thrash, not slowness)
TA-throttle CPU frequency collapse / thermal throttle (the other "slow" story)

Problems this kills

Killer searches

Who this is for

SREs, homelab network engineers, and anyone who has had to defend a switch against an application developer with confidence.

Next

All Use Cases Browse All Apps