Getting Data In

Failed to parse epoch timestamp for Checkpoint Opsec

rsimmons
Splunk Employee
Splunk Employee

Splunk isn’t recognizing the date from the opsec.logs since the date is being sent in a localized format

Tags (1)
0 Karma

rsimmons
Splunk Employee
Splunk Employee

This can be resolve by modifying DATESTAMP = epoch (“unix”) and by doing this don't need to set TZs. You will need to edit DATESTAMP properties under fw1-loggrabber.conf file so that it is indexed properly.

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 ...