Getting Data In


Overview of data preview

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

Overview of data preview

The Splunk Enterprise data preview feature offers a powerful way to improve event processing. You can use it to make sure that Splunk Enterprise indexes your data exactly as you want it to appear.

Data preview lets you see how your indexed data will look, while also allowing you to easily make adjustments to improve the outcome. It runs a subset of your data through the normal indexing process but, unlike normal indexing, it does not commit the resulting events to an index. During data preview, you can adjust and improve the indexing process interactively, so, when Splunk Enterprise later performs the actual indexing, your event data ends up in the index formatted exactly as you want it to be.

New for Splunk Enterprise 6.1, the data preview feature lets you preview structured data and change how Splunk Enterprise displays the data by selecting various kinds of commonly-known data types.

Here is an example of the main data preview screen:

61 datapreview.png

During data preview, you can adjust how Splunk Enterprise processes timestamps and event breaks. Once you're satisfied with the results, you can save your changes as a new source type, which you can then apply to your actual data. See "Data preview and source types" for details.

Data preview operates only on single files, but with a bit of planning you can also preview data from network or directory inputs. See "Prepare your data" for details.

Note: Data preview is a Splunk app. It ships as part of Splunk Enterprise and gets enabled at start-up.

This documentation applies to the following versions of Splunk: 6.1 , 6.1.1 , 6.1.2 , 6.1.3 , 6.1.4 , 6.1.5 , 6.1.6 , 6.1.7 , 6.1.8 , 6.1.9 View the Article History for its revisions.

You must be logged into 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!