ll three Beats templates render an empty setup.kibana: block, so no Kibana endpoint is configured. When a beat loads dashboards (e.g. metricbeat runs a bare metricbeat setup, which includes --dashboards), it falls back to the default localhost:5601. In a full stack Kibana usually runs on another host, so dashboard loading targets the wrong host or fails.
Populate setup.kibana.host from the known Kibana host in a full stack (with the credentials/TLS already used for the ES output), and allow overriding it standalone. Only relevant when dashboards are loaded.
ll three Beats templates render an empty setup.kibana: block, so no Kibana endpoint is configured. When a beat loads dashboards (e.g. metricbeat runs a bare metricbeat setup, which includes --dashboards), it falls back to the default localhost:5601. In a full stack Kibana usually runs on another host, so dashboard loading targets the wrong host or fails.
Populate setup.kibana.host from the known Kibana host in a full stack (with the credentials/TLS already used for the ES output), and allow overriding it standalone. Only relevant when dashboards are loaded.