You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2022. It is now read-only.
For our purposes, I had to change the metadata host value from 'node.hostname' to 'node.fqdn'.
With just hostname we only get the short hostname in Splunk. In our case we have multiple hosts with the same hostname in different domains, so knowing that "foo" failed to converge doesn't help, we need to know that "foo.bar.example.com" failed.
Not sure if this can be easily changed for everyone or if it will affect existing users negatively. Or could it be an attribute added to the splunk_handler cookbook to toggle hostname or fqdn usage.
The text was updated successfully, but these errors were encountered:
For our purposes, I had to change the metadata host value from 'node.hostname' to 'node.fqdn'.
With just hostname we only get the short hostname in Splunk. In our case we have multiple hosts with the same hostname in different domains, so knowing that "foo" failed to converge doesn't help, we need to know that "foo.bar.example.com" failed.
Not sure if this can be easily changed for everyone or if it will affect existing users negatively. Or could it be an attribute added to the splunk_handler cookbook to toggle hostname or fqdn usage.
The text was updated successfully, but these errors were encountered: