topic Re: inputs.conf -> time_before_close in Getting Data In

inputs.conf -> time_before_close

lpolo — Mon, 28 Sep 2020 13:12:03 GMT

Have any of you had the necessity to use time_before_close in inputs.conf. if so could you share your scenario?
I am having an issue with a source log where events could be quite large. Therefore, some events are not broken correctly.

Thanks,
Lp

Re: inputs.conf -> time_before_close

sowings — Mon, 28 Sep 2020 14:32:19 GMT

I have a log file which is a large XML document comprised of various sub-documents that take a while to run. Each job writes its data to the file as the output is generated, but the whole XML document isn't closed (appropriate closing tags, etc) until the whole set of jobs is complete. Sometimes, the writing of the log will pause for more than 3 seconds (the default value of time_before_close), and so Splunk was consuming that file half-way through.

If you're seeing events broken before they're complete, consider MAX_EVENTS (it defaults to 256 additional lines, so if you have those multi-line events showing a linecount of 257, this could be the issue), or possibly TRUNCATE.

Re: inputs.conf -> time_before_close

lpolo — Fri, 09 Aug 2013 14:33:32 GMT

Thanks for your comment. It is not my scenario.