Getting Data In

Log event skipped on read

cdstealer
Contributor

Hi,
I'm generating a stats (csv) file that is updated every second. The log has no errors/skips, but I've found that if I don't specify an interval within inputs.conf it will miss randomly and/or part read the last event as it's written. If I set an interval, say 10 seconds, then I get a missed event every 10 seconds without fail. I'm using collectl to populate the file.
So I guess my question is; is it possible to skip the last event, but read it on the next run?

Here are my inputs and props for completeness.

inputs.conf

[monitor:///var/tmp]
whitelist = sysRes-log-\d{8}\.tab
disabled = false
index = os
host = logserver
sourcetype = sysStats
#multiline_event_extra_waittime = true
recursive = false

props.conf

[sysStats]
DATETIME_CONFIG =
FIELD_DELIMITER = space
INDEXED_EXTRACTIONS = csv
KV_MODE = none
LINE_BREAKER = ([\r\n]+)
NO_BINARY_CHECK = true
PREAMBLE_REGEX = (^##|^#\s)
SHOULD_LINEMERGE = false
TIMESTAMP_FIELDS = Date,Time
TIME_FORMAT = %Y%m%d %H:%M:%S
BREAK_ONLY_BEFORE_DATE = true
category = Structured
description = Space value format. Set header and other settings in "Delimited Settings"
disabled = false
pulldown_type = true
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!

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

Data Management Digest – May 2026

Welcome to the May 2026 edition of Data Management Digest!   As your trusted partner in data innovation, the ...