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
Description of the problem including expected versus actual behavior:
The visualizations and dashboards that ship with various beats should use the beat.name field rather than beat.hostname, because we have better control over the beat.name field.
For example, my MacOS laptop's hostname changes based on DHCP,
but all my beat configuration files set the beat.name to a consistent value.
I would like the metricbeat dashboards to use this value.
I discussed this issue with Jim Goodwin at the Toronto Elastic (ON)Tour event last week and he suggested I should create an issue on github to describe the problem.
Steps to reproduce:
run metricbeat on my laptop at home, where my hostname is radicalfywsscom.local
take my laptop to work, where the hostname changes to radical.architech.lan
view the metricbeat dashboard, and observe that the "Top Hosts by CPU" thinks these are 2 different hosts when in fact there is only 1
I would much prefer to see the Host as "radical.fywss.com", which is the beat.name in my metricbeat.yml file
please see attached screen shots, which show that beat.name contains the value I would like to see in my dashboards
Thanks!
The text was updated successfully, but these errors were encountered:
Kibana version: 6.0.0-rc1
Elasticsearch version: 6.0.0-rc1
Server OS version: MacOS Sierra 10.12.6
Browser version: n/a
Browser OS version: n/a
Original install method: download page
Description of the problem including expected versus actual behavior:
The visualizations and dashboards that ship with various beats should use the beat.name field rather than beat.hostname, because we have better control over the beat.name field.
For example, my MacOS laptop's hostname changes based on DHCP,
but all my beat configuration files set the beat.name to a consistent value.
I would like the metricbeat dashboards to use this value.
I discussed this issue with Jim Goodwin at the Toronto Elastic (ON)Tour event last week and he suggested I should create an issue on github to describe the problem.
Steps to reproduce:
Thanks!
The text was updated successfully, but these errors were encountered: