Getting Data In

Do not index some events from a log source...

lpolo
Motivator

Hi,

I have a log source that is causing some problems. I think it is caused by events like this ones:

29-02-2012 18:00:58 UTC udb_persona_ingest INFO - ========= JOB COUNTERS ======== 
29-02-2012 18:00:58 UTC udb_persona_ingest INFO - ========= JOB COUNTERS END ======== 

how can I configure splunk to not index this particular event that is linked to a sourcetype.

Thanks in advanced.
Lp

Tags (1)
0 Karma

mikelanghorst
Motivator

Look for the section titled: Discard specific events and keep the rest on this link RouteAndFilterData

You'll just need to create a regex that matches those 2 log entries. The data will still be read and sent from a UF to the indexer, but the indexer will simply discard the messages.

Something similar to the following
props.conf on your indexer:
[your_sourcetype]
TRANSFORMS-null= discard

transforms.conf on your indexer:
[setnull]
REGEX = "=+\s(?:JOB COUNTERS|JOB COUNTERS END)\s=+"
DEST_KEY = queue
FORMAT = nullQueue

Might need to tweak the regex a bit, but that should work.

lpolo
Motivator

Thanks I will test it tomorrow.

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...