autoregress
Description
Prepares your events for calculating the autoregression, or the moving average, by copying one or more of the previous values for field into each event.
The first few events will lack the augmentation of prior values, since the prior values do not exist.
Syntax
autoregress <field> [AS <newfield>] [ p=<int> | p=<int>-<int> ]
Required arguments
- field
- Syntax: <string>
- Description: The name of a field. Most usefully a field with numeric values.
Optional arguments
- p
- Syntax: p=<int> | p=<int>-<int>
- Description: Specifies which prior events to copy values from. You can specify a single integer or a numeric range. For a single value, such as 3, the
autoregress
command copies field values from the third prior event into a new field. For a range, theautoregress
command copies field values from the range of prior events. For example, if you specify a range such asp=2-4
, then the field values from the second, third, and fourth prior events are copied into new fields. - Default: 1
- newfield
- Syntax: <field>
- Description: If
p
is set to a single integer, thenewfield
argument specifies a field name to copy the single field value into. Invalid ifp
is set to a range.
If the newfield
argument is not specified, the single or multiple values are copied into fields with the names <field>_p<num>. For example, if p=2-4
and field=count
, the field names are count_p2, count_p3, count_p4.
Usage
The autoregress
command is a centralized streaming command. See Command types.
Examples
Example 1:
For each event, copy the 3rd previous value of the 'ip' field into the field 'old_ip'.
... | autoregress ip AS old_ip p=3
Example 2:
For each event, copy the 2nd, 3rd, 4th, and 5th previous values of the 'count' field.
... | autoregress count p=2-5
Since the new field
argument is not specified, the values are copied into the fields 'count_p2', 'count_p3', 'count_p4', and 'count_p5'.
Example 3:
Calculate a moving average of event size over the current event and the four prior events. This search omits the moving_average for the initial events, where the field would be wrong, because summing null fields is considered null.
... | eval rawlen=len(_raw) | autoregress rawlen p=1-4 | eval moving_average=(rawlen + rawlen_p1 + rawlen_p2 + rawlen_p3 +rawlen_p4 ) /5
See also
audit | awssnsalert |
This documentation applies to the following versions of Splunk® Enterprise: 7.0.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10, 7.0.11, 7.0.13, 7.1.0, 7.1.1, 7.1.2, 7.1.3, 7.1.4, 7.1.5, 7.1.6, 7.1.7, 7.1.8, 7.1.9, 7.1.10, 7.2.0, 7.2.1, 7.2.2, 7.2.3, 7.2.4, 7.2.5, 7.2.6, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.3.0, 7.3.1, 7.3.2, 7.3.3, 7.3.4, 7.3.5, 7.3.6, 7.3.7, 7.3.8, 7.3.9, 8.0.0, 8.0.1, 8.0.2, 8.0.3, 8.0.4, 8.0.5, 8.0.6, 8.0.7, 8.0.8, 8.0.9, 8.0.10, 8.1.1, 8.1.2, 8.1.3, 8.1.4, 8.1.5, 8.1.6, 8.1.7, 8.1.8, 8.1.9, 8.1.13, 8.1.14, 8.2.0, 8.2.1, 8.2.2, 8.2.3, 8.2.4, 8.2.5, 8.2.6, 8.2.7, 8.2.8, 8.2.9, 8.2.10, 8.2.11, 8.2.12, 9.0.0, 9.0.1, 9.0.2, 9.0.3, 9.0.4, 9.0.5, 9.0.6, 9.0.7, 9.0.8, 9.0.9, 9.0.10, 9.1.0, 9.1.1, 9.1.2, 9.1.3, 9.1.4, 9.1.5, 9.1.6, 9.2.0, 9.2.1, 9.2.2, 9.2.3, 9.3.0, 9.3.1, 8.1.0, 8.1.10, 8.1.11, 8.1.12
Feedback submitted, thanks!