Getting Data In

WinEventLog question

santiagn
Path Finder

hi

i added the below to my inputs.conf and restarted the forwarder service but when i search my host it still does not return any wineventlogs. am i missing something or doing something wrong?

[WinEventLog://Application]
disabled = 0

[WinEventLog://Security]
disabled = 0

[WinEventLog://System]
disabled = 0

Tags (1)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi santiagn,
if you want to ingest Windows Event Logs the easiest way is to install on Forwarder Splunk_TA_Windows, enabling only stanzas that you want.

Anyway, in your inputs.conf there isn't any index so try inserting in your search index=main

If there still aren't any logs, verify if your indexer receives logs from the forwarder using this search index=_internal host=your_host
In this way you verify if your forwarder is correctly connected to Indexer.

If not, verify firewalls ans outputs.conf in your forwarder.
If you have _internal logs, verify that forwarder and indexer are time aligned and that Windows on forwarder create logs (verify policies).

Bye.
Giuseppe

View solution in original post

0 Karma

clara-fication
Super Champion

I have been facing the same issue. Check to make sure your ports are allowed to send data.

go to the Windows Firewall with Advanced Security and check the inbound rules. look for the port your host is on. if it isn't there, add a rule for it, and see if that fixes any issues.

Solution Clara-fied!
0 Karma

santiagn
Path Finder

thanks! but i should've mentioned that i have cpu load and avail memory already working just the wineventlog stanza wasn't.

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi santiagn,
if you want to ingest Windows Event Logs the easiest way is to install on Forwarder Splunk_TA_Windows, enabling only stanzas that you want.

Anyway, in your inputs.conf there isn't any index so try inserting in your search index=main

If there still aren't any logs, verify if your indexer receives logs from the forwarder using this search index=_internal host=your_host
In this way you verify if your forwarder is correctly connected to Indexer.

If not, verify firewalls ans outputs.conf in your forwarder.
If you have _internal logs, verify that forwarder and indexer are time aligned and that Windows on forwarder create logs (verify policies).

Bye.
Giuseppe

0 Karma

santiagn
Path Finder

adding index=main made it work.

thanks so much!

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!

Splunk Enterprise Security: An Automated Phishing Response Workflow

Originally posted on Splunk.com.   Key takeaways  The volume of phishing emails can overwhelm even the most ...

Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...