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
We use heartbeat inputs to monitor the availability of our Logstash instances.
Unfortunately, the host field is automatically set to the FQDN hostname via Socket.gethostname. Depending on the environment, it may be desireable to change this, e.g. to a certain IP for machines with multiple interfaces, or to only the host part of FQDN, etc. Current workaround is to tag heartbeat messages and apply a mutate filter in Logstash config.
Please expose the host field via configuration parameter in order to allow setting a custom value. Big thanks!
The text was updated successfully, but these errors were encountered:
We use heartbeat inputs to monitor the availability of our Logstash instances.
Unfortunately, the host field is automatically set to the FQDN hostname via
Socket.gethostname
. Depending on the environment, it may be desireable to change this, e.g. to a certain IP for machines with multiple interfaces, or to only the host part of FQDN, etc. Current workaround is to tag heartbeat messages and apply a mutate filter in Logstash config.Please expose the host field via configuration parameter in order to allow setting a custom value. Big thanks!
The text was updated successfully, but these errors were encountered: