Splunk Enterprise Security

Splunk Enterprise Security: Expected Host Not Reporting finds hosts that are reporting with a different name. How to fix this?

edonze
Path Finder

Expected Host Not Reporting finds results for hosts that are reporting with a different name; for instance, the short DNS name rather than the fqdn, or the IP address rather than the hostname.
Is there a way to fix this?

sshres5
Communicator

what does your hostname -f return?

Add your FQDN on the /etc/hosts, that should provide you the FQDN.

Also, you can add "host = hostname" field in the inputs.conf on the forwarder

0 Karma

syahiya
Engager

I think @edonze is looking for a solution to the Correlation Rule "Expected Host Not Reporting " in Enterprise Security App. We are also facing the same issue and thus we are getting lot of false positive alerts.

0 Karma

hardikJsheth
Motivator

Check out asset table on your ES app.
This table contains field called "is_expected" which determines if host is going to be reported by the mentioned correlation search. If you are getting incorrect values as hostname check the asset table and update it as required.

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!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...