Buffers events from real-time search to emit them in ascending time order when possible.
rtorder [discard=<bool>] [buffer_span=<span-length>] [max_buffer_size=<int>]
- Syntax: buffer_span=<span-length>
- Description: Specify the length of the buffer. Default is 10 seconds.
- Syntax: discard=<bool>
- Description: Specifies whether or not to always discard out-of-order events. Default is false.
- Syntax: max_buffer_size=<int>
- Description: Specifies the maximum size of the buffer. Default is 50000, or the
max_result_rowssetting of the [search] stanza in limits.conf.
The rtorder command creates a streaming event buffer that takes input events, stores them in the buffer in ascending time order, and emits them in that order from the buffer only after the current time reaches at least the span of time given by buffer_span after the timestamp of the event.
Events will also be emitted from the buffer if the maximum size of the buffer is exceeded.
If an event is received as input that is earlier than an event that has already been emitted previously, that out of order event will be emitted immediately unless the discard option is set to true. When discard is set to true, out of order events will always been discarded, assuring that the output is always strictly in time ascending order.
Example 1: Keep a buffer of the last 5 minutes of events, emitting events in ascending time order once they are more than 5 minutes old. Newly received events that are older than 5 minutes are dicarded if an event after that time has already been emitted.
... | rtorder discard=t buffer_span=5m
Have questions? Visit Splunk Answers and see what questions and answers the Splunk community has using the rtorder command.
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 , 4.2 , 4.2.1 , 4.2.2 , 4.2.3 , 4.2.4 , 4.2.5 , 4.3 , 4.3.1 , 4.3.2 , 4.3.3 , 4.3.4 , 4.3.5 , 4.3.6 , 4.3.7 , 5.0 , 5.0.1 , 5.0.2 , 5.0.3 , 5.0.4 , 5.0.5 , 5.0.6 , 5.0.7 , 6.0 , 6.0.1 , 6.0.2