Getting Data In

Universal Forwader Hostname issues

sreejithpoothu
New Member

I have a universal forwader insatlled on AWS cloud instance.As autoscaling is set,when it met certain conditions,this instance will terminate and new instance will be created.But the issue is that on the new instance inputs.conf showing the old hostname,is there any way for splunk to automatically detect the hostname.Please help.

Tags (1)
0 Karma

sreejithpoothu
New Member

we are using splunk version 4.3.2.

0 Karma

sreejithpoothu
New Member

Hi Mario,

When i am doing it manually,hostname not changing.Stopped splunk and removed host entry in inputs.conf and removed guid in server.conf.Then started splunk still splunk not able to populate the hostaname.

0 Karma

MarioM
Motivator

is your /etc/hosts and /etc/hostname being updated?

are your able to try with 4.3.4?

0 Karma

sreejithpoothu
New Member

OS in ubuntu12.04

0 Karma

sreejithpoothu
New Member

we are using splunk version 4.3.2.

0 Karma

MarioM
Motivator

it should...which version of splunk and OS are you running?

0 Karma

MarioM
Motivator

no you will need to do something similar to this similar question : universal-forwarder-on-dhcp-address

0 Karma
Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...