Monitoring Splunk

Splunk Broken Hosts App Alerting False Postives

NightShark
Path Finder

Greetings Fellow Splunkers,

We have been recieving false reports claiming certain index, sourcetype and ip combinations that havent been communicating for a long time, however when checking over we do actually seem to be recieving a healthy amount of logs from the combination of fields mentionned above.

I have seen this in 2 other organizations aswell, what are some recommended fixes for this issue? has anyone else come across the same problem?

Thanks,

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 ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...