All Apps and Add-ons

Why are Windows Event IDs delayed?

m_khatibo88
New Member

Windows Event IDs (Codes) logs are delayed for days. Latency varies, The delay reaches at times weeks or months. It is confirmed that none of the pipeline queues are blocked.

Note that the Event IDs are reached in real-time in the event viewer

Labels (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

How do the events get from Windows to Splunk?  Is it via WMI or an installed forwarder?  The latter is preferred.  If a UF is used, is it always running?

---
If this reply helps you, Karma would be appreciated.
0 Karma

m_khatibo88
New Member

Yes the Windows forwarded events from UF and I receive logs in real-time (running) from all inputs except (Events ID) which has a delay of months.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...