All Apps and Add-ons

Remove syslog data in transforms.com

jotne
Builder

I have a Splunk Heavy Forwarder server that is a rsyslog server as well.

When Splunk sees the syslog data, it sets the source type, then the index name before its sent to indexing.

props.conf

 

[rsyslog]
TRANSFORMS-force_vmware = force_sourcetype_vmware, force_ix_vmware

 

 transforms.conf

 

force_sourcetype_vmware]
SOURCE_KEY = MetaData:Host
REGEX = ^host::(10\.30\.31\.\d+)
DEST_KEY = MetaData:Sourcetype
FORMAT = sourcetype::esxi


[force_ix_vmware]
SOURCE_KEY = MetaData:Sourcetype
REGEX = ^sourcetype::(?i)esxi$
DEST_KEY = _MetaData:Index
FORMAT = vmware

 

 

This works fine.

I now like to remove all lines (that are from vmware) that starts with:

 

<134>2021.....
<166>2021.....

 

 

To do so, I made a regex like this:

 

REGEX = ^<(134|166)>2021

 

 

I know that to remove some, I should use:

 

DEST_KEY = queue
FORMAT = nullQueue

 

 

But I do not get it to work.  How to make sure only remove correct data from vmware only?

Labels (1)
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!

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...