Splunk Search

Event time inconsistency

shangshin
Builder

Hi,
I have a stanza below defined in transforms.conf.

[wip_fields]
DELIMS = ","
FIELDS = timestamp,wip,vip

Strangely, the event time is not consistent with the timestamp in each record. It seems the event time is always 5 hours ahead of the timestamp. I suspect I need to set the timezone explicitly? Please share some thoughts or suggestion. Thanks!

table _time,timestamp

8/20/12 4:30:17.000 AM  08/20/2012 09:30:17
Tags (3)
1 Solution

dwaddle
SplunkTrust
SplunkTrust

If the system parsing the events (normally the indexer, but could be a heavy forwarder) is in a different timezone than the data being indexed, then you will need to provide a TZ offset. Use a props.conf config entry of the form:

[sourcetype]
TZ=America/Chicago

This is an index-time setting so you will have to reload previously indexed data.

View solution in original post

dwaddle
SplunkTrust
SplunkTrust

If the system parsing the events (normally the indexer, but could be a heavy forwarder) is in a different timezone than the data being indexed, then you will need to provide a TZ offset. Use a props.conf config entry of the form:

[sourcetype]
TZ=America/Chicago

This is an index-time setting so you will have to reload previously indexed data.

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!

Analytics Workspace deprecation

As of Splunk Cloud Platform 10.4.2604 and Splunk Enterprise 10.4, Analytics Workspace is now deprecated. ...

Splunk Developer Day Recap: Building, Publishing, and Growing on the Splunk Platform

Splunk Developer Day brought the Splunk developer community together for a practical look at what it means to ...

[Puzzles] Solve, Learn, Repeat: Matching cron expressions

This puzzle (first published here) is based on matching timestamps to cron expressions.All the timestamps ...