Dashboard
/
Splunk Core Certified User
/ Notes
Alerts
Study cheat sheet Β· SPLUNK-CORE
Generated May 13, 2026
Practice This Topic
Key Concepts
- Alerts are saved searches that run on a schedule or in real-time and trigger actions when conditions are met
- Created from the Search & Reporting app by saving a search as an alert
- Two trigger types: Scheduled (runs at defined intervals) and Real-time (continuous monitoring)
- Alert conditions define when the alert fires: number of results, custom condition, field value, etc.
- Alert actions include: Send Email, Run Script, Add to Triggered Alerts, Use a Webhook, and others via add-ons
- Alerts are stored in the Triggered Alerts dashboard (Activity > Triggered Alerts)
- Alert severity levels: Info, Low, Medium, High, Critical
- Throttling prevents alert fatigue by suppressing repeated alerts for a defined time period or per field value
How It Works
- A saved search runs on a schedule (e.g., every 5 minutes, hourly, cron expression) or in real-time
- Splunk evaluates the trigger condition against search results
- If condition is met, the alert fires and executes configured actions
- Throttle settings control whether the alert fires again immediately or waits
- Triggered alerts are logged and visible in the Triggered Alerts page for 24 hours by default
Commands / Syntax / Key Values
| Setting | Options / Notes |
|---|---|
| Schedule | Run on Cron Schedule, Every Hour, Every Day, etc. |
| Trigger Condition | Number of Results, Number of Hosts, Number of Sources, Custom Condition |
| Trigger Once vs Per-Result | "Once" fires one action; "For each result" fires an action per matching event |
| Throttle period | Suppress for X seconds/minutes/hours; optionally per field value |
| Severity | Info / Low / Medium / High / Critical |
| Alert Actions | Email, Webhook, Run Script, Add to Triggered Alerts, Slack (via add-on) |
| Expires | Triggered Alerts list entry expires after 24 hours by default |
| Permissions | Private by default; can be shared to App or Global |
Exam Gotchas
- Real-time alerts β scheduled alerts β Real-time runs continuously but is resource-intensive; exam questions may try to swap these concepts
- "Per Result" throttling β Throttling by field value (e.g., suppress per
host) means each unique value is tracked separately; a common confusion point with global throttle - Triggered Alerts vs Alert Actions β "Add to Triggered Alerts" is itself an action you must explicitly enable; alerts don't automatically appear there unless this action is selected
- Scheduled alert timing β If you choose a cron schedule, the search runs over the time window you define, not just at that moment; students often confuse schedule time with search time range
- Permissions matter β An alert saved as Private is only visible to its owner; sharing to App makes it available to other users in that app β exam may test who can see/edit alerts
Quick Summary
Alerts in Splunk are saved searches that run on a schedule or in real-time and fire actions (email, webhook, script, etc.) when a defined trigger condition is met. The key settings to master are: trigger condition (what makes it fire), throttle (how often it can re-fire), and actions (what happens when it fires). Remember that "Add to Triggered Alerts" must be explicitly selected as an action, real-time alerts are continuous and resource-heavy, and alert visibility depends on permission settings (Private vs App vs Global).
My Notes
Edit your saved notes here. Saving replaces what is stored.
Add More Notes
Paste new content here. It will be added below your existing notes β nothing gets overwritten.