Getting Data In

Indexing only partial events

thiru25
Explorer

Hello, I have 1000s files that I am indexing but I only need first 3 fields to be indexed in each event, is there an efficient way to do this?

Here is an example: Log header with tab delimited fields, I only need to index first 3 fields "v1 Time | Datagrams | Messages" and discard other garbage.

v1 Time Datagrams Messages Total missed datagrams Total retransmission requests Total unrecognized messages Total
processed messages Total ignored messages Total invalid messages Last rx

Thanks,
Thiru.

Tags (2)
0 Karma

btt
Path Finder

Hi
I think you can do it by configure file setups for index-time field extractions

When Splunk Enterprise reads file, if there are colums with empty row it does not index that header field or any of the rows in
it. This means that neither header or any of the data in its row can be searched for in the index.

So if your unwanted fieldshave empty rows(all rows) splunk would not indexed them.
You can read about Props.conf attributes for structured data in data manual.
see the MISSING_VALUE_REGEX attribute

Hope,this could help

0 Karma

btt
Path Finder

I find the answer below who seems similar with your question
http://answers.splunk.com/answers/42260/index-only-part-of-a-log.html

is this what you where looking for?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...