Getting Data In

Help with props.conf to detect timestamp

power12
Communicator

Hello Splunkers,

 

I have the following raw event.It was parsing with correct date and time until the daylight saving started but after march 13th(daylight saving started) I see one hour mismatch..what changes should I make on props.conf to show the correct time?

 

3/13/22
11:59:59.989 PM
 
2022-03-13 22:59:59,989 |v144031v~212657|*** conn[SSL/TLS]=103 CLIENT(1.1.2.2:23) disconnected.

Thanks in Advance

Labels (1)
Tags (2)
0 Karma

sperkins
Path Finder

You can set your Timezone in props.conf 

example: 

[host::nyc*]
TZ = US/Eastern

https://docs.splunk.com/Documentation/Splunk/latest/Data/Applytimezoneoffsetstotimestamps

0 Karma

isoutamo
SplunkTrust
SplunkTrust

I have seen that there are still some e.g. network equipments which needs reboot after summer/normal time has changed. But as @PickleRick said you should try to get TZ information on source side into events. Then there shouldn't be any issues with it especially when source system and splunk indexer/heavy forwarder are in different time zone!

r. Ismo

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Ideally, you should have timezone information within the timestamp. Otherwise, if you know timezone the timestamp is reported in (and it's not prone to change with daylight saving), you can set the timezone explicitly for the given source or sourcetype.

0 Karma
Get Updates on the Splunk Community!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

New Release | Splunk Cloud Platform 10.1.2507

Hello Splunk Community!We are thrilled to announce the General Availability of Splunk Cloud Platform 10.1.2507 ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...