Accurate parsing in Splunk Cloud begins with defining clean source types using props.conf attributes: TIME_FORMAT (strptime pattern), TIME_PREFIX (anchor regex before the timestamp), MAX_TIMESTAMP_LOOKAHEAD, SHOULD_LINEMERGE, LINE_BREAKER, and TRUNCATE.
For high-throughput single-line or structured JSON/syslog streams, setting SHOULD_LINEMERGE = false alongside an explicit LINE_BREAKER = ([\r\n]+) improves parsing performance by avoiding unnecessary multiline regex merging. Always verify TRUNCATE (default 10000 bytes) if large JSON payloads are being clipped.
Where those props.conf settings live depends on your Cloud architecture. In Victoria Experience, installing an app via SSAI or ACS automatically pushes index-time props.conf and transforms.conf to the indexer tier, whereas in Classic or Heavy Forwarder architectures, parsing occurs on the first full Splunk instance (HF) or requires Support coordination.
[app:audit:json]
TIME_PREFIX = "timestamp"\s*:\s*"
TIME_FORMAT = %Y-%m-%dT%H:%M:%S.%3N%Z
MAX_TIMESTAMP_LOOKAHEAD = 32
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
TRUNCATE = 32768