Documentation > Splunk > User Manual > Identify transactions

User Manual

 


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

Identify transactions

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

Identify transactions

A transaction is a meta-event, a collection of events that you want to group together. Transactions can span multiple sources.

A transaction type is a configured type of transaction that is saved as a field in Splunk.

A common transaction search use is to group multiple events into a single meta-event that represents a single physical event. For example, an out of memory problem could trigger several database events to be logged, and they can all be grouped together into a transaction. Use the transaction command to define a transaction or override transaction options specified in transactiontypes.conf.

Example: Run a search that groups together all of the web pages a single user (or client IP address) looked at, over a time range.

This search takes events from the access logs, and creates a transaction from events that share the same clientip value that occurred within 5 minutes of each other (within a 3 hour time span).

sourcetype=access_combined | transaction fields=clientip maxpause=5m maxspan=3h

For more information, including use cases and examples, see the "Group events into transactions" chapter of the Knowledge Manager manual.

Retrieved from "http://docs.splunk.com/Documentation/Splunk/4.0.1/User/AboutTransactions"

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.

Feedback submitted, thanks!