One of the common issues we see in the Infrastructure UI is that when shipping data from the same host for Metricbeat and Filebeat, the host.name does not match up. The Filebeat host.name typically ends up looking like filebeat-{some kind of hash id} instead of the actual system hostname. This results in the following nodes on the waffle map:

When you click on the filebeat- prefixed hosts to view the metric, you end up with nothing. Until this is fixed we can't move forward with plans to add logging metrics OR a log view to our detail page for any of the hosts. This also affects our Logging UI for all hosts (with metrics) because host.name doesn't match any of the hosts logs; essentially "View logs" for hosts is broken.
One of the common issues we see in the Infrastructure UI is that when shipping data from the same host for Metricbeat and Filebeat, the
host.namedoes not match up. The Filebeathost.nametypically ends up looking likefilebeat-{some kind of hash id}instead of the actual system hostname. This results in the following nodes on the waffle map:When you click on the
filebeat-prefixed hosts to view the metric, you end up with nothing. Until this is fixed we can't move forward with plans to add logging metrics OR a log view to our detail page for any of the hosts. This also affects our Logging UI for all hosts (with metrics) becausehost.namedoesn't match any of the hosts logs; essentially "View logs" for hosts is broken.