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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

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

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...