Getting Data In

WindowsUpdateLog

yuvalba
Path Finder

Hi,
I have Splunk for Windows installed and want to check the WindowsUpdate log.
I am receiving the log correctly and have setup sourcetype to be WindowsUpdateLog as needed.
However I don't have any fields extracted.
I tested by applying the transform pid-tid-component_for_windowsupdatelog manually as:

rex "^\S+\s+\S+\s+(?<pid>\S+)\s+(?<tid>\S+)\s+(?<component>\S+)"

And the fields are extracted correctly.
Why aren't they being extracted on regular search? I must be missing something...
Thanks

Tags (2)
0 Karma
1 Solution

yuvalba
Path Finder

Found the problem.
The fields objects (transform and report) where by default configured in App context only so did not work on the Search app.
Changing the relevant objects to Global makes it work as expected.

View solution in original post

0 Karma

yuvalba
Path Finder

Why can't I edit my post?
Whem I try to edit the title and save, it say "This field is required" under "update summary" although I fill it up.

0 Karma

yuvalba
Path Finder

Found the problem.
The fields objects (transform and report) where by default configured in App context only so did not work on the Search app.
Changing the relevant objects to Global makes it work as expected.

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...