Getting Data In

2 Different Timezones being interpreted with the same IIS log file

derekho55
Explorer

As with many folks, my IIS logs are setup to run with GMT timestamps. I have setup "TZ=GMT" on the sourcetype setup for my IIS logs, set in the indexer under props.conf.

I have multiple IIS servers using the same source type. For most of my servers, all is well and I see that Splunk is converting the timezone to my local timezone (Pacific) based on my settings. However, there are a few servers that I see Splunk is interpretting 2 different timezones, see below:


10/21/19
7:35:55.000 AM

2019-10-21 07:35:55 10.1.24.88 GET /api/..snip.. - 80 - 10.1.24.81 - - 200 0 0 6
host = V-WEB-PA-2-P **source = C:\inetpub\logs\logfiles\W3SVC22\u_ex191021.log
* sourcetype = ms:iis:default*

10/21/19
7:35:54.000 AM

*2019-10-21 14:35:54 10.1.24.88 POST /api/..snip.. - 80 - 10.1.24.88 - - 200 0 0 2

host = V-WEB-PA-2-P source = C:\inetpub\logs\logfiles\W3SVC22\u_ex191021.log sourcetype = ms:iis:default*

Splunk is interpreting log entries with "7:35:xx" and 14:35:xx" as both IIS logs that have happened at 7:35:xx Localtime. The correct and expected interpretation is only log entries with "14:35:xx" should be interpreted that way.

You will notice that the same file is being used to make the two interpretations.

Can anyone please point me in the direction of where I may have mis-configured Splunk, or why this is happening?

Thank you.

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!

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

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...