Knowledge Management

Overriding event times in Splunk logs

siaavush
New Member

The problem is that there is a lag happening in the log shipping from our application to Splunk, after some investigation we realized that we can override the event time by providing _time property in the logs (ref:https://docs.splunk.com/Documentation/SCS/current/Search/Timestampsandtimeranges) and it should be UNIX epoch time (seconds).
we did that but it didn’t have any effect on the event time and the time difference persists.
It has been a while since we are testing a lot of possibilities yet none of them did the trick.

Labels (3)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The cited manual describes how to use _time in a search, but the problem you describe happens at index time and so is not covered by that manual.

Please tell us how the log gets from your application to Splunk.  Also, how much lag are you seeing?  Is there a sourcetype defined in props.conf for the data?  If so, what are the settings?  Can you share a (sanitized) sample event or two?

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...