fieldsummary

Description

The fieldsummary command calculates summary statistics for all fields or a subset of the fields in your events. The summary information is displayed as a results table.

Syntax

fieldsummary [maxvals=<num>] [<wc-field-list>]

Optional arguments

maxvals

Syntax: maxvals=<num>

Description: Specifies the maximum distinct values to return for each field.

Default: 100

wc-field-list

Description: A field or list of fields that can include wildcarded fields.

Usage

The fieldsummary command displays the summary information in a results table. The following information appears in the results table:

Field name

Description

field

The field name in the event.

count

The number of events/results with that field.

distinct_count

The number of unique values in the field.

is_exact

Whether or not the field is exact. This is related to the distinct count of the field values. If the number of values of the field exceeds maxvals, then fieldsummary will stop retaining all the values and compute an approximate distinct count instead of an exact one. 1 means it is exact, 0 means it is not.

max

If the field is numeric, the maximum of its value.

mean

If the field is numeric, the mean of its values.

min

If the field is numeric, the minimum of its values.

numeric_count

The count of numeric values in the field. This would not include NULL values.

stdev

If the field is numeric, the standard deviation of its values.

values

The distinct values of the field and count of each value.

Examples

Example 1:

Return summaries for all fields from the _internal index for the last 15 minutes.

index=_internal earliest=-15m latest=now | fieldsummary

Example 2:

Returns summaries for fields in the _internal index with names that contain "size" and "count". The search returns only the top 10 values for each field from the last 15 minutes.

fieldsummary

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

Feedback submitted, thanks!

You must be logged into splunk.com in order to post comments.
Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic.
If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk,
consider posting a question to Splunkbase Answers.