Quantcast
Channel: Questions in topic: "splunk-enterprise"
Viewing all articles
Browse latest Browse all 47296

Why are the transforms on indexer props being broken by the extractions on my forwarder's props?

$
0
0
Whenever I enable this EXTRACTION stanza on my universal forwarder, my TRANSFORM extraction stops working on my indexer: [web_app_logs] NO_BINARY_CHECK = 1 INDEXED_EXTRACTIONS = TSV PREAMBLE_REGEX = ^#.* FIELD_DELIMITER=\t The indexer props with the TRANSFORM line that stops working (I added the input time stuff as redundancy during testing): [web_app_logs] TRANSFORMS-AutoSourceType = AutoSourceType NO_BINARY_CHECK = 1 INDEXED_EXTRACTIONS = TSV PREAMBLE_REGEX = ^#.* FIELD_DELIMITER=\t SHOULD_LINEMERGE = False MAX_TIMESTAMP_LOOKAHEAD = 50 TZ = UTC TIME_FORMAT = %s.%6Q TRUNCATE = 250000 The forwarder's props extraction stanza should be fine according to [this][1], and it does indeed work by parsing my tsv files correctly. The specific commands for field extractions can be found [here][2]. For context the TRANSFORM is setting the events to new sourcetypes depending on a string found within them. What am I missing? Why is my forwarder's props.conf interferring with my indexer's props.conf stuff that comes after input time stuff? Does one override the other? I tried putting my TRANSFORM into the forwarder's props.conf but that doesn't work either (as expected since it's not a heavy forwarder). [1]: https://wiki.splunk.com/Where_do_I_configure_my_Splunk_settings%3F [2]: http://docs.splunk.com/Documentation/Splunk/latest/Data/Extractfieldsfromfileswithstructureddata

Viewing all articles
Browse latest Browse all 47296

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>