Our private cloud uses a standard naming convention that isn't very useful, and people use aliases to make the hosts meaningful. Is there a way to get the deployment server to recognize these aliases? I tried entering them in the serverclass, and they are just ignored.
Converted this to the answer. You should use the clientName field to endow randomly assigned hostnames with a meaningful name. You can take this further by defining your own naming convention so your serverclass can have wildcard matching for sending classes based on the naming convention (and therefore based on the function or data points you need to collect).
messy solution: add the aliases to
/etc/hosts or the corresponding windows file.
clean solution: ask your network / DNS team to create CNAME's for the private cloud hosts and use them.
Hope this helps ...
Ah now I understand your request....
I have no DNS available to modify host entries and test it, but my assumption is that Splunk uses
A records or
NAME records. If I recall it correct you could only overcome such a situation by using the messy solution on the deployment server........
Here was my work-around.. looking for a sanity review.
The install is done via a chef recipe, which also puts the deployment file structure down, and the regional outputs structure down. If an alias is requested as part of the serverclass install (to allow me to more easily segregate the hosts), then the chef recipe will create another directory structure, which will contain another deployment.conf, but only with this info:
clientName = myalias
I did this manually and it seemed to work. Thoughts?