Getting Data In

Strange data comes out as field values. Same as the source path

nmnank
Engager

I have a strange problem.

In the search header, the value of the field created in props.conf is the same as the source path.

SH - props.conf
LOOKUP-center_tag_dest = ldcc_portal_asset IP AS dest OUTPUT group_id AS tag_dest

result
alt text

Normal values ​​also appear but some of these problems are found

I want to know what is the cause and how to solve it.

0 Karma

nmnank
Engager

result
source::udp:20001|host::61.111.55.40|ips_sniperips_evt

0 Karma

nmnank
Engager

Strange data found in source type that doesn't match stanza

props.conf
stanza - [(?::){0}*_*_*_*]

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...