Getting Data In

How to stop ingesting a field value

franciscof
Explorer

Hi guys, I have an input made from the ASplunk addon for AWS and what I want to do is to stop ingesting a field value. This is cloudflare data and what I want to stop ingesting is the field value WAFAction=unknown

Could I do this through the props and transforms? If so, how should I do it?

Thanks in advance.

 

Regards,

Labels (2)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

So you want to not ingest the field WAFAction, but only if the value is "unknown", correct?  I'm curious about the use case for that.  You may be able to do it with INGEST_EVAL.  Here's an untested transform:

[dropunknownwafaction]
INGEST_EVAL = WAFAction:=if(WAFAction="unknown", null(), WAFAction)
---
If this reply helps you, Karma would be appreciated.
0 Karma

franciscof
Explorer

Actually is the other way around. I do not want to ingest that specific field value (WAFAction=unknown). How could I do?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

That is why my answer does.  It only ingests the WAFAction field if the value is not "unknown".

---
If this reply helps you, Karma would be appreciated.
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!

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

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