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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

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