icon/x Created with Sketch.

Splunk Cookie Policy

We use our own and third-party cookies to provide you with a great online experience. We also use these cookies to improve our products and services, support our marketing campaigns, and advertise to you on our website and other websites. Some cookies may continue to collect information after you have left our website. Learn more (including how to update your settings) here.
Accept Cookie Policy

We are working on something new...

A Fresh New Splunkbase
We are designing a New Splunkbase to improve search and discoverability of apps. Check out our new and improved features like Categories and Collections. New Splunkbase is currently in preview mode, as it is under active development. We welcome you to navigate New Splunkbase and give us feedback.

Accept License Agreements

This app is provided by a third party and your right to use the app is in accordance with the license provided by that third-party licensor. Splunk is not responsible for any third-party apps and does not provide any warranty or support. If you have any questions, complaints or claims with respect to this app, please contact the licensor directly.

Thank You

Downloading split
SHA256 checksum (split_101.zip) 2deef9d6fb75c9a069d33bdb990153f80612c59822c87590c82a707b5cb40b63
To install your download
For instructions specific to your download, click the Details tab after closing this window.

Flag As Inappropriate

splunk

split

This app has been archived. Learn more about app archiving.
This app is NOT supported by Splunk. Please read about what that means for you here.
Overview
Details
This is a command that will split an event into multiple events based on a regular expression.

There are a few occasions when log messages can end up lumped together. Sometimes it's because the log format has changed, sometimes the configuration was made badly, and sometimes things just go wonky.

To help deal with this a little, I've created this command for you lovely people to use called split. Using this command, you specify a regular expression that describes the beginning of a new event. For example, the log format for app foo changed yesterday, so we ended up with a bunch of entries in splunk that were blobbed together.

sourcetype="foo" | split start="^\d+-"

In this case, the pattern says "one or more numbers, followed by a dash, at the beginning of a line". This matches "2010-" at the beginning of the log messages in question.

You can then further filter the events, if you only want some of them:

sourcetype="bar" error | split start="^\d+-" | search error

Caveats...
All of the field values from the previous message are copied along. This includes the date, so the date will be whatever was at the beginning of the chunk. If you need a field in the split log message, then they will need to be reparsed using kv, rex or eval.

Feel free to drop me a note.

Vincent Bumgarner
vincent.bumgarner at gmail.com

Release Notes

Version 1.0.1
June 30, 2010

Subscribe Share

Are you a developer?

As a Splunkbase app developer, you will have access to all Splunk development resources and receive a 10GB license to build an app that will help solve use cases for customers all over the world. Splunkbase has 1000+ apps from Splunk, our partners and our community. Find an app for most any data source and user need, or simply create your own with help from our developer portal.

Follow Us:
Splunk, Splunk>,Turn Data Into Doing, Data-to-Everything, and D2E are trademarks or registered trademarks of Splunk Inc. in the United States and other countries. All other brand names,product names,or trademarks belong to their respective owners.