How search works
This documentation does not apply to the most recent version of Splunk.
This documentation applies to the following versions of Splunk: 3.2 , 3.2.1 , 3.2.2 , 3.2.3 , 3.2.4 , 3.2.5 , 3.2.6
How search works
Splunk includes a powerful search language for crafting simple to sophisticated searches. To learn more about Splunk's search syntax, see the User Manual search reference section. Here are a few other things you can do with your searches.
Saved searches
Saved searches are search strings that have been saved for reuse. Saving a search allows for capture of useful and lengthy strings. Splunk ships with a few pre-configured, useful saved searches:
- Daily indexing volume by server
- Errors in the last 24 hours
- KB indexed per hour last 24 hours
- Messages by minute last 3 hours
- Splunk errors last 24 hours
- all
Share a saved search or save it as private. Shared and personally owned private saved searches appear by default on the bottom of the landing page:
Saved searches allow for knowledge capture and sharing. Splunk administrators can create saved searches to distribute to all their Splunk users. You may wish to distribute saved searches in bundle directories to other systems in your data center. Learn more about bundle directories.
Form search and Macro search
- Macro searches are saved searches with variables. Fill in the variables at search time.
- Form searches work just like macro searches, but include an additional interface for searching.
Alerting
Set any saved search to run on a specific schedule, trigger alerts, send emails or RSS feeds. Learn more about setting up alerts via Splunk Web or the savedsearches.conf file.
Alerts can also trigger shell scripts. This is one way to configure Splunk to work with other applications. Two examples include sending SNMP traps and sending syslog events.
Live Tail
Use Live Tail to watch data streaming into Splunk. Live tail works just like tail -f in *nix systems. Learn more about Live Tail