Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kibana visualizations should rely on beat.name rather than beat.hostname #14332

Closed
stuvie opened this issue Oct 5, 2017 · 3 comments
Closed

Comments

@stuvie
Copy link

stuvie commented Oct 5, 2017

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:

  1. run metricbeat on my laptop at home, where my hostname is radicalfywsscom.local
  2. take my laptop to work, where the hostname changes to radical.architech.lan
  3. 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
  4. I would much prefer to see the Host as "radical.fywss.com", which is the beat.name in my metricbeat.yml file
  5. please see attached screen shots, which show that beat.name contains the value I would like to see in my dashboards
    Thanks!

screen shot 2017-10-05 at 12 41 30 pm

screen shot 2017-10-05 at 12 43 06 pm

@epixa
Copy link
Contributor

epixa commented Oct 5, 2017

@tsg @simianhacker

@tsg
Copy link
Contributor

tsg commented Oct 5, 2017

@stuvie Agreed, and this was reported in elastic/beats#5276 as well. I'm currently working on a fix, you can watch that issue for updates.

@tsg
Copy link
Contributor

tsg commented Oct 5, 2017

Closing as the Beats repo is the better place for this issue, but thank you for the very well described issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants