Getting Data In

Splunk_TA_Windows - script:installedapps timestamp issues?



Thought I posted this before, but can't find it in my history. 

I am seeing alerts in my Splunk logs statin that the I am getting data from the future on my sourcetype  script:installedapps. It's default and unmodified from the Splunk_TA_Window standard.

From there I did notice that _indextime and _time were off a bit. 

When I look at props.conf provided by Splunk_TA_Windows it has no time stamp recognition. Is there a reason for this? Should I go ahead and add it or is there a trick for this I am missing? 




Labels (1)
0 Karma


So I went ahead and created a basic props.conf per my undertanding of best practice. 


My latency between time and indexed time was about -80second on this sourcetype. After adding the below props.conf to a local override I am now getting closer to 10 seconds. 

Didn't think props.conf would so dramatically impact a single sourcetype like that, but I guess it could? Either way no longer getting the data from the future error either. 


# props.conf
 pulldown_type = true
 category = Windows
 description = List Installed Apps
 ### Index time
 # Input queue - event_breaker processed at the UF as well as IDX
 EVENT_BREAKER = ([\r\n]+)\d{4}\-\d{2}\-\d{2}\s+\d{1,2}:\d{2}:\d{2}.\d{3}
 TIME_FORMAT= %Y-%m-%d %H:%M:%S.%3Q
 # Typing queue
 # Indexing queue
 SEGMENTATION = indexing
 # Search time
 EVAL-data_classification = "Proprietary"
0 Karma
Get Updates on the Splunk Community!

Improve Your Security Posture

Watch NowImprove Your Security PostureCustomers are at the center of everything we do at Splunk and security ...

Maximize the Value from Microsoft Defender with Splunk

 Watch NowJoin Splunk and Sens Consulting for this Security Edition Tech TalkWho should attend:  Security ...

This Week's Community Digest - Splunk Community Happenings [6.27.22]

Get the latest news and updates from the Splunk Community here! News From Splunk Answers ✍️ Splunk Answers is ...