Getting Data In

Why is our 6.4.1 Windows universal forwarder not appearing in the list of hosts?

Grenage1
Engager

Good afternoon,

I'm testing out Splunk. I have installed Splunk Light on a VM, and installed a few forwarders. The first few machines were 2003, so I installed an older forwarding agent (6.1.10). That went just fine and the hosts are listed in the default search page; I've successfully created reports based on the security event logs.

My next machine is 2012 R2, so I've installed the Universal Forwarder (6.4.1) - the host is not appearing in the list, and typing host= into the search bar suggests only the aforementioned servers are matches. I added an entry to inputs.conf:

[WinEventLog://Security]
disabled = false

Alas, no change. I can see that there is an established connection in netstat, but that's about it.

Any tips on where to go next?

0 Karma
1 Solution

Grenage1
Engager

The current forwarder was using index "Wineventlog", rather than "main", which the older forwarders used by default. I've stipulated the index name in the input file, and entries are now correctly displayed - the server also shows under the "what to search" page.

I will accept and close this, as it was down to a misunderstanding on how data was forwarded.

View solution in original post

0 Karma

Grenage1
Engager

The current forwarder was using index "Wineventlog", rather than "main", which the older forwarders used by default. I've stipulated the index name in the input file, and entries are now correctly displayed - the server also shows under the "what to search" page.

I will accept and close this, as it was down to a misunderstanding on how data was forwarded.

0 Karma
Get Updates on the Splunk Community!

Buttercup Games: Further Dashboarding Techniques (Part 6)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...

Technical Workshop Series: Splunk Data Management and SPL2 | Register here!

Hey, Splunk Community! Ready to take your data management skills to the next level? Join us for a 3-part ...

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...