#Splunk transaction series#
#Splunk transaction download#

In other cases, it's usually better to use the stats command, which performs more efficiently, especially in a distributed environment. When it is desirable to see the raw text of the events combined rather than an analysis on the constituent fields of the events. In other cases, when an identifier is reused, for example in DHCP logs, a particular message may identify the beginning or end of a transaction.Ģ. In this case, time spans or pauses are also used to segment the data into transactions. This is the case when the identifier is reused, for example web sessions identified by cookie or client IP. When a unique ID (from one or more fields) alone is not sufficient to discriminate between two transactions. The transaction command is most useful in two specific cases:ġ. Additionally, it retains the raw event and other field values from the original event and enables you to group events using much more complex criteria, such as limiting the grouping by time span or delays and requiring terms to define the start or end of a group. On the other hand, except for the duration between first and last events and the count of events, the transaction command does not compute statistics over the grouped events. The stats command is meant to calculate statistics on events grouped by one or more fields and discard the events (unless you are using eventstats or streamstats). Anytime you can filter the search before the first pipe, the faster the search runs.įor more examples, see the transaction command.īoth the stats command and the transaction command are similar in that they enable you to aggregate individual events together based on field values. There is no filtering before the transaction command. Additionally, this search is run over all events. You won't see it in this data, but some transactions may take a long time because the user is updating and removing items from his shopping cart before he completes the purchase. You might be curious about why the transactions took a long time, so viewing these events might help you to troubleshoot. The values in the duration field show the difference, in seconds, between the timestamps for the first and last events in the transaction. The where filter cannot be applied before the transaction command because the duration field is added by the transaction command. This example then pipes the transactions into the where command and the duration field to filter out all of the transactions that took less than a second to complete. The endswith='purchase' argument does the same for the last event in the transaction. The search defines the first event in the transaction as events that include the string, 'view', using the startswith='view' argument. Sourcetype=access_* | transaction JSESSIONID clientip startswith='view' endswith='purchase' | where duration>0 This example defines a transaction as a group of events that have the same session ID, JSESSIONID, and come from the same IP address, clientip, and where the first event contains the string, 'view', and the last event contains the string, 'purchase'. This example searches for transactions with the same session ID and IP address. Use the time range All time when you run the search.

#Splunk transaction download#

To try this example on your own Splunk instance, you must download the sample data and follow the instructions to get the tutorial data into Splunk. Transaction search example This example uses the sample data from the Search Tutorial but should work with any format of Apache web access log. To learn more, see Identify and group events into transactions in this manual.

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. One common use of a transaction search is to group multiple events into a single meta-event that represents a single physical event.

Use the transaction command to define a transaction or override transaction options specified in nf. Any number of data sources can generate transactions over multiple log entries.Ī transaction search is useful for a single observation of any physical event stretching over multiple logged events. A transaction type is a configured transaction, saved as a field and used in conjunction with the transaction command.

#Splunk transaction series#

A transaction is any group of conceptually-related events that spans time, such as a series of events related to the online reservation of a hotel room by a single customer, or a set of events related to a firewall intrusion incident.