Getting Data In

How can I immediately verify my changes have put these host's new events in the correct TZ?

woodams
Explorer

I have a number of hosts sending logs "in the future". I've configured my indexer's props.conf to adjust the TZ for the select few problem children and restarted the indexer.

How can I immediately verify my changes have put these host's new events in the correct TZ (meaning, no longer in the future)

Basically the existing "future events" are making the timeline noisy and I can't see where (or perhaps *when*) new events are coming in. I could wait several hours for them to clear out, but that's not ideal.

Labels (2)
0 Karma

andrew_nelson
Communicator

Quickest way is to get the most recently indexed event and check what _time its being indexed at.
First set your search timeframe to Today or Earliest : -1d Latest : +1d. (This will catch TZ errors. Anything more than 1 day in the future is likely not TZ issue)

You can access the actual time your indexer processed the event with _indextime.

Something like: 

 

 

index=abc sourcetype=xyz host=123
| eval time=_time, index_time=_indextime 
| eval _time=index_time 
| stats latest(time) as lastLog 
| convert ctime(lastLog)

 

By swapping in the time the indexer processed the events for _time, you can get the latest values based on the most recently received events and not the time they were indexed at.

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

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