Hey there,
using ELK v.7.15.2 I was trying to import Heartbeat dashboards into Kibana.
I set the following parameters:
setup.dashboards.enabled: true
but I am facing the following error:
Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing directory /usr/share/heartbeat/kibana: Failed to import dashboard: The directory /usr/share/heartbeat/kibana/7 is empty, nothing to import
Into the /kibana/7 folder there is a subfolder named dashboard with a ndjson file. is that correct? I cannot find any clear documentation about that.
Recent versions of heartbeat do not have dashboards.. the ./kibana directory is empty. I checked all the way back to 7.7.0, i.e. there are no dashboards to load / setup.
Just On a side note for beats setup.. you may not want to load the dashboards with every container deploy either that is wasteful as well / slows down the deployment (example pretty heavy for filebeat / metricbeat)... that said it should work..
We see some customer with a pattern such as deploy a "canary/config" deployment that loads / setups and then the actual "workload" containers that just run.
I am using 7.15 heartbeat version.
Since ES disks will be permanent, probably I will use the "canary approach" at least at the first time. If I try to use heartbeat setup -e
should I populate any folder or similar?
The setup command loads and setups up the associated assets (index templates, ingest pipelines, dashoard, ML Jobs etc..etc..) in kibana and Elasticsearch.
It really only needs to be run once per version of the beat. (or if you make some other significant changes but that is not really the case for heartbeat)
You run setup once... to set up the assets and then deploy 1... or 1,000 heartbeats
Some beats and modules have many assets (filebeat) some have few heartbeat.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.