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

Heartbeat Kibana saved search has the wrong field (dashboard does not work with the default configuration) #4852

Closed
pmusa opened this issue Aug 9, 2017 · 1 comment

Comments

@pmusa
Copy link

pmusa commented Aug 9, 2017

  • Version: 6.0.0-beta1-linux-x86_64
  • Operating System: Ubuntu
  • Steps to Reproduce:
    Start Heartbeat with the -setup flag and then, in Kibana, access the Heartbeat dashboard to see No results found message. Digging a bit, I found that every visualization in the auto-loaded dashboard is configured with the Heartbeat "saved search", which is currently using monitor.name instead of monitor.type.

I am not sure if monitor.name was deprecated in favor of monitor.type or if there is another problem. Also, in the same "saved search" there is a meta field that also accesses monitor.name. Maybe it needs to be changed as well.

@urso
Copy link

urso commented Aug 9, 2017

monitor.name is freely configurable by users, to potentially differentiate between monitors of same type. If not configured, monitor.name defaults to monitor.type. The bug is monitor.name being empty.

Did you find monitor.name being used for filtering (like monitor.name: http) or for display only? For filtering we should use monitor.type and for display monitor.name.

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

No branches or pull requests

2 participants