- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
_joe
Contributor
01-29-2025
03:27 AM
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.
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
_joe
Contributor
01-29-2025
03:28 AM
I updated it to a 4 digit year to match my logs.
%d %b %Y %H:%M:%S, %Z
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
_joe
Contributor
01-29-2025
03:28 AM
I updated it to a 4 digit year to match my logs.
%d %b %Y %H:%M:%S, %Z
