Getting Data In

Why is Splunk ignoring my [<sourcetype>] in props.conf?

Grady
Engager

I've been fighting with what seems to be a simple configuration to input a nonstandard text format for 2 days now. The only configuration that I believe I need in the sourcetype stanza in props is a BREAK_ONLY_BEFORE. The configuration makes perfect sense but it simply isn't working. In fact, when I manually set the sourcetype the indexer finds no events at all. When left on automatic it finds events but they're not valid or malformed.

Tags (1)
0 Karma
1 Solution

Grady
Engager

After a full day of poring over the answers here, I find this buried away where it took forever to find:

http://answers.splunk.com/questions/7191/log-file-not-breaking-correctly/7211#7211

And what do you know. There were a number of incorrect assumptions tucked away in the learned app files, including some entries in files other than props. Cleaning those out made everything work like the magic I was expecting.

Thanks meno!

View solution in original post

Grady
Engager

After a full day of poring over the answers here, I find this buried away where it took forever to find:

http://answers.splunk.com/questions/7191/log-file-not-breaking-correctly/7211#7211

And what do you know. There were a number of incorrect assumptions tucked away in the learned app files, including some entries in files other than props. Cleaning those out made everything work like the magic I was expecting.

Thanks meno!

Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...