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

Break the Build: Inside the KubeDoom Lounge at .conf26

    You step up to the machine. The pixelated corridors of a certain 1993 FPS load in front of you, EMP Pulse ...

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...