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
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.
The text was updated successfully, but these errors were encountered:
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.
Start Heartbeat with the
-setup
flag and then, in Kibana, access the Heartbeat dashboard to seeNo 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 usingmonitor.name
instead ofmonitor.type
.I am not sure if
monitor.name
was deprecated in favor ofmonitor.type
or if there is another problem. Also, in the same "saved search" there is a meta field that also accessesmonitor.name
. Maybe it needs to be changed as well.The text was updated successfully, but these errors were encountered: