Getting Data In

How to ignore the import data

pansplunktest
New Member

Hi,

I using the external data source named: firewall and I want to ignore the data

"Apr  2 16:06:15 firewall device_id=abcde1234  [Root]system-critical-00033: Src IP session limit! From a.b.c.d to i.j.k.l, proto 1 (zone Trust int  ethernet0/3). Occurred 2 times. (2013-04-02 16:06:14)"

which content "From a.b.c.d"

I tried to config "props.conf"

[source::firewall]
TRANSFORMS-null = setnull

[setnull]
REGEX = From\sa.b.c.d
DEST_KEY = queue
FORMAT = nullQueue

But is shown the warning "

Possible typo in stanza [setnull] in /opt/splunk/etc/system/local/props.conf, line 5: REGEX  =  From\sa.b.c.d
Possible typo in stanza [setnull] in /opt/splunk/etc/system/local/props.conf, line 6: DEST_KEY  =  queue"
Possible typo in stanza [setnull] in /opt/splunk/etc/system/local/props.conf, line 7: FORMAT  =  nullQueue

Is it how I modify to correct config? Thanks in advance.

Tags (1)
0 Karma

pansplunktest
New Member

Thanks. That is missing to creating tranforms.conf

0 Karma

Ayn
Legend

The setnull transform should go into transforms.conf, not props.conf. Read the docs, here: http://docs.splunk.com/Documentation/Splunk/5.0.2/Deploy/Routeandfilterdatad#Discard_specific_events...

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...