Getting Data In

Time config incorrect

_joe
Contributor

This isn't so much a question as a comment. I found that time config to be incorrect. 

My logs start like this:
{"Time": "29 Jan 2025 03:16:30, PST",

The default timestring is expecting a 2 digit year.

 

%d %b %y %H:%M:%S, %Z

 

Prior to the update, Splunk was stil able to figure out the time but issed the timezone parameter. In other words, if your heavy forwarder has the same timezone as your zScaler logs you would probably be fine.

 

 

Labels (1)
0 Karma
1 Solution

_joe
Contributor

I updated it to a 4 digit year to match my logs. 

%d %b %Y %H:%M:%S, %Z

 

View solution in original post

0 Karma

_joe
Contributor

I updated it to a 4 digit year to match my logs. 

%d %b %Y %H:%M:%S, %Z

 

0 Karma
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!

Event Series May & June: From Network Visibility to Service Intelligence

Unifying the Network: Moving from Alert Noise to Service Intelligence with Splunk ITSI In today’s hybrid ...

Global Splunk User Group Events: May + June 2026

Your Splunk Community Awaits: Discover Upcoming User Group Events Worldwide    Staying ahead in the fast-paced ...

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...