Splunk Search

Host Field is Using the Old Hostname

ibraheem
Explorer

Hi,

I'm facing an issue with 5 hosts, recently we change the hostname of these machines but it is not reflected in the host field, in the host field the old hostname is shown.

Below is a sample log:

"LogName=Security

EventCode=4673

EventType=0

ComputerName=A0310PMTHYCJH15.tnjhs.com.pk

host = A0310PMNIAMT05    source = WinEventLog:Security     sourcetype = WinEventLog "

We are receiving logs from these windows hosts through UF and I checked the apps deployed in these hosts and checked the inputs.conf, hostname field is not defined.

The new hostname is shown in the logs in the field ComputerName.

Any suggestions to this problem would be appreciated.

Labels (1)
0 Karma

ibraheem
Explorer

Logs are landing directly from UF to indexers

0 Karma

ibraheem
Explorer

In the newly ingested events, the old hostname is used in the host field, the new hostname is shown in the ComputerName field

0 Karma

PickleRick
SplunkTrust
SplunkTrust

That is indeed strange. Do you have TA_windows installed on your receiving end?

0 Karma

ibraheem
Explorer

Yes, we have TA_windows installed. I've checked this add-on for hostname/host field in inputs.conf, but this field does not exist

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Are you sending directly from your UF to indexer(s)? Or do you have a HF somewhere in the middle?

0 Karma

PickleRick
SplunkTrust
SplunkTrust

Are you talking about the old events or the newly ingested ones?

0 Karma
Get Updates on the Splunk Community!

Enterprise Security Content Update (ESCU) | New Releases

In December, the Splunk Threat Research Team had 1 release of new security content via the Enterprise Security ...

Why am I not seeing the finding in Splunk Enterprise Security Analyst Queue?

(This is the first of a series of 2 blogs). Splunk Enterprise Security is a fantastic tool that offers robust ...

Index This | What are the 12 Days of Splunk-mas?

December 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...