Getting Data In

Linebreaker for ESXi Logs

rfiscus
Path Finder

I am having problems getting the line breaking to work. The below events are showing as one event with the below set in my Props.conf file which is installed on the Indexers.

Feb 18 08:11:04 10.10.10.10 sshd[2910906]: Accepted keyboard-interactive/pam for user@domain from 10.10.10.10 port 54258 ssh2
Feb 18 08:11:04 10.10.10.10 sshd[2910906]: pam_unix(sshd:session): session opened for user user@domain by (uid=0)
Feb 18 08:11:04 10.10.10.10 sshd[2910906]: Session opened for 'user@domain' on /dev/char/pty/t0
Feb 18 08:11:04 10.10.10.10 shell[2910915]: Interactive shell session started
Feb 18 08:11:05 10.10.10.10 vmkernel: cpu39:2098112)NMP: nmp_ResetDeviceLogThrottling:3575: last error status from device mpx.vmhba32:C0:T0:L0 repeated 5 times

[VMware:ESXi]
TIME_PREFIX = ^
MAX_TIMESTAMP_LOOKAHEAD = 15
TZ = CT
KV_MODE = none
ANNOTATE_PUNCT = false
TIME_FORMAT = %b %d %H:%M:%S
LINE_BREAKER = ([\n]+)\w{3}\s.\w\s\w{2}:\w{2}:\w{2}
SHOULD_LINEMERGE = False
TRUNCATE = 750

Any idea why the line breaking is not working?

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Are you sure the line separator is right? Try LINE_BREAKER = ([\r\n]+)\w{3}\s.\w\s\w{2}:\w{2}:\w{2}

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Are you sure the line separator is right? Try LINE_BREAKER = ([\r\n]+)\w{3}\s.\w\s\w{2}:\w{2}:\w{2}

---
If this reply helps you, Karma would be appreciated.

rfiscus
Path Finder

Looks like I was missing the \r for the carriage return, odd because it had been working for a long time, I wonder if VMware changed their log format in 6.5+ of ESXi. Anyhow, thanks for noticing that, works normal again.

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!

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...