Documentation > Splunk > User Manual > Monitor recurring situations

User Manual

 


Welcome
Splunk Overview
Index New Data
Search and Investigate
Search Examples and Walkthroughs
Capture Knowledge
Automate Monitoring
Analyze and Report

Monitor recurring situations

This documentation does not apply to the most recent version of Splunk. Click here for the latest version.

Monitor recurring situations

If you've read the preceding chapters you have a pretty good idea of how to use Splunk's powerful search capabilities to learn all kinds of things about the event data in your system. But this doesn't help you with the myriad of recurring situations that everyone in IT is faced with on a regular basis. You can't be running searches yourself all of the time.

This is why we've designed Splunk to be the most flexible monitoring tool in your arsenal. Every search you design can be set up to run automatically on a regular schedule. And any scheduled search can be configured to send alert messages to you and other interested parties when specific circumstances are met. You can base these alerts on a wide range of threshold and trend-based scenarios, including empty shopping carts, brute force firewall attacks, and server system errors.

In this chapter you'll learn how to:

Retrieved from "http://docs.splunk.com/Documentation/Splunk/4.0.6/User/MonitoringRecurringSituations"

This documentation applies to the following versions of Splunk: 4.0 , 4.0.1 , 4.0.2 , 4.0.3 , 4.0.4 , 4.0.5 , 4.0.6 , 4.0.7 , 4.0.8 , 4.0.9 , 4.0.10 , 4.0.11 View the Article History for its revisions.


You must be logged into splunk.com in order to post comments. Log in now.

Was this documentation topic helpful?

If you'd like to hear back from us, please provide your email address:

We'd love to hear what you think about this topic or the documentation as a whole. Feedback you enter here will be delivered to the documentation team.