Getting Data In

Path of props.conf and transforms.conf

prajnasaha
Loves-to-Learn

I'd like to monitor log files and ingest specific lines from these files. My props.conf and transforms.conf has no error. But for some reason the props.conf is not working and instead of indexing specific lines , it is indexing the whole log. Is there any specific path to place .conf files, or any other solution?

0 Karma

glc_slash_it
Path Finder

Hi,

can you paste your confs here? Usually the proper way of doing it would look something like this:

transforms.conf
[filter_some_events]
REGEX = <regex_that_matches_the_events_you_want>
DEST_KEY = _MetaData:Index
FORMAT = <your_index>

props.conf
[<sourcetype_stanza>]
...other_props_configs...
TRANSFORMS-filter_name = filter_some_events

 

0 Karma

prajnasaha
Loves-to-Learn

Hi @glc_slash_it , here it is. Although I am not getting the specific lines, instead the whole log is getting indexed.

 

transforms.conf
[err_line]
REGEX = ^(?!.error)
DEST_KEY = _MetaData:Index
FORMAT = error_idx

props.conf
[err_src]
TRANSFORMS-err_line = err_line

 

 

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