Getting Data In

failed to parse timestamp for event

keiichilam
Explorer

HI

My splunk failed to parse timestamp of one of the inbound syslog.

10-03-2011 10:55:18.119 +0800 WARN DateParserVerbose - Failed to parse timestamp for event. Context="source::udp:514|host::TSSSYSLOG01|syslog|" Text="172.18.12.21, -, -, N, 2011-10-03, 11:02:45, 1, -, -, ProxyAV_Sec, 172.18.12.25, 1344, 906, 193, 0, ..."

I have renamed the sourcetype as proxyav in transforms.conf

in props.conf, I added follow
[proxyav]

SHOULD_LINEMERGE = false

# MAX_TIMESTAMP_LOOKAHEAD=60

# TIME_PREFIX = ^[^\,]+\,[^\,]+\,[^\,]+\,[^\,]+\,\s

# TIME_FORMAT = %Y-%m-%d, %T

# TIME_PREFIX = ^[^\,]+\,[^\,]+\,[^\,]+\,[^\,]+\,\s

TIME_FORMAT = %Y-%m-%d, %H:%M:%S,

KV_MODE = none

I did also tried various remarked setting, but no luck to remove the parse error. Could anyone give me a hand?

Best Regards

Tags (3)
0 Karma

mzorzi
Splunk Employee
Splunk Employee

You should use the TIME_PREFIX, instead of ^[^,], I would use a regex for the ip, then a non space, like \S

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!

Developer Spotlight with Denis Gladkikh

From Splunk Engineer to Kubernetes App Builder Denis GladkikhWhat happens when a lifelong developer turns a ...

Governing Enterprise AI, Bringing Cisco Telemetry Home, and More from Splunk Lantern

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

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...