⛏️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 Sentinel Watchtower • Room 2

Static, Sudden Change, Historical Anomaly & Resource Running Out

Splunk Infrastructure Monitoring offers four built-in alert conditions alongside Custom SignalFlow to match detection logic to your workload.

Static Threshold triggers when a metric crosses a fixed constant (for instance, error_rate > 5%), making it ideal for hard SLAs. Sudden Change compares a short current window against an immediately preceding window to catch abrupt spikes or drops regardless of baseline level. Historical Anomaly compares the current window against cyclical historical windows (such as the same hour over previous days or weeks), catching deviations in diurnal traffic.

Resource Running Out fits a linear trajectory to bounded resources—such as disk usage, memory pools, or license quotas—and alerts proactively before the resource hits 100% capacity (for example, projected to exhaust within 24 hours).

Choosing the Right Built-in Condition
SLA Latency > 500ms       -> Static Threshold
Abrupt 3x Error Spike     -> Sudden Change
Low Checkout on Monday AM -> Historical Anomaly
Disk Full in < 24 Hours   -> Resource Running Out
Never use a Static Threshold for metrics with strong daily or weekly cycles like login volume—Historical Anomaly catches unexpected drops during peak hours without paging during quiet overnight hours.

Knowledge Check

Prove your understanding to clear the room (Rewards XP)
❤️❤️❤️
Question 1 of 2
An e-commerce platform sees 50,000 logins per hour at noon and 2,000 per hour at 3:00 AM. You need an alert if noon traffic suddenly drops to 10,000 logins per hour without false-paging at 3:00 AM. Which built-in condition should you choose?
AStatic Threshold
BResource Running Out
CHistorical Anomaly
DHeartbeat / Missing Data only