About monitoring transaction performance
This documentation does not apply to the most recent version of Splunk. Click here for the latest version.
About monitoring transaction performance
The simplest kind of monitoring is to start with a search that you have already used to find and troubleshoot a problem. Then you can save the search, schedule it to run regularly, and set up an alert that fires when the results are outside a happy range.
This topic shows you how to: search for slow transactions across tiers, create a saved search and set an alert, create and use an event type to group events, summarize events using the timechart command, and create a report that runs regularly.
The walkthrough uses the set up outlined in the [Documentation:AppManagement:DataSources Index data] walkthrough. You have a multi-tier application that allows phone subscribers to activate and manage their accounts over the web. Your logs include web logs, J2EE logs, API logs, and database error logs from servers spread across three domains in three different regions of the United States.
This documentation applies to the following versions of Splunk: 4.1 , 4.1.1 , 4.1.2 , 4.1.3 , 4.1.4 , 4.1.5 , 4.1.6 , 4.1.7 , 4.1.8 View the Article History for its revisions.