Getting Data In

Need help parsing Venafi logs

miuwang
New Member

We are feeding Venafi logs into Splunk and have trouble with records breaking at the wrong places.

This is the format of the input - all log records start with this:
10.213.32.41,4/16/2018 11:06 AM,0001001D,...
IP date time 8 hex-character event ID

and can have multiple lines per record.

Can someone suggest sourcetype configuration to correctly parse our logs?

Tags (1)
0 Karma

somesoni2
Revered Legend

Try this (props.conf on your indexer/heavy forwarder)

[Venafi_Logs]
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)(?=\d{1.3}\.\d{1.3}\.\d{1.3}\.\d{1.3},\d+\/\d+\/\d+\s\d+\:\d+)
TIME_PREFIX = ^\d{1.3}\.\d{1.3}\.\d{1.3}\.\d{1.3},
TIME_FORMAT = %m/%d/%Y %H:%M %p
MAX_TIMESTAMP_LOOKAHEAD = 19
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!

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...

Ditch the Manual Grind: Building AI Agents with Splunk

Ditch the Manual Grind: Building AI Agents with Splunk Let’s be real: your team’s time is being eaten alive. ...

Cisco Data Fabric from Architecture to Investigation, Better SOC Visibility, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...