# Metricbeat does not install dashboards when running setup

**URL:** <https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [May 15, 2018, 10:09pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006 "2018-05-15T22:09:50Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![shanim](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@shanim](https://discuss.elastic.co/u/shanim)\
**Post date:** [May 15, 2018, 10:09pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/1 "2018-05-15T22:09:50Z")

</div>

Metricbeat 6.2.3 reports a failure when attempting to install the kibana dashboards as the command expects the kibana/6 folder to be in the bin folder and not in the /usr/share/metricbeat/kibana folder.

```auto
[root@abcrd006 metricbeat]# ./bin/metricbeat -setup -e -c /etc/metricbeat/metricbeat.yml
2018-05-15T17:04:12.511-0500 INFO instance/beat.go:468 Home path: [/usr/share/metricbeat/bin] Config path: [/usr/share/metricbeat/bin] Data path: [/usr/share/metricbeat/bin/data] Logs path: [/usr/share/metricbeat/bin/logs]
2018-05-15T17:04:12.511-0500 DEBUG [beat] instance/beat.go:495 Beat metadata path: /usr/share/metricbeat/bin/data/meta.json
2018-05-15T17:04:12.511-0500 INFO instance/beat.go:475 Beat UUID: 297d1be6-de9a-4a87-acf5-eddc1d70ed54
2018-05-15T17:04:12.511-0500 INFO instance/beat.go:213 Setup Beat: metricbeat; Version: 6.2.3
2018-05-15T17:04:12.511-0500 DEBUG [beat] instance/beat.go:230 Initializing output plugins
2018-05-15T17:04:12.511-0500 DEBUG [processors] processors/processor.go:49 Processors:
2018-05-15T17:04:12.512-0500 INFO pipeline/module.go:76 Beat name: abcrd006
2018-05-15T17:04:12.512-0500 DEBUG [modules] beater/metricbeat.go:80 Register [ModuleFactory:[docker, mongodb, mysql, postgresql, system, uwsgi], MetricSetFactory:[aerospike/namespace, apache/status, ceph/cluster_disk, ceph/cluster_health, ceph/cluster_status, ceph/monitor_health, ceph/osd_df, ceph/osd_tree, ceph/pool_disk, couchbase/bucket, couchbase/cluster, couchbase/node, docker/container, docker/cpu, docker/diskio, docker/healthcheck, docker/image, docker/info, docker/memory, docker/network, dropwizard/collector, elasticsearch/node, elasticsearch/node_stats, etcd/leader, etcd/self, etcd/store, golang/expvar, golang/heap, graphite/server, haproxy/info, haproxy/stat, http/json, http/server, jolokia/jmx, kafka/consumergroup, kafka/partition, kibana/status, kubernetes/container, kubernetes/event, kubernetes/node, kubernetes/pod, kubernetes/state_container, kubernetes/state_deployment, kubernetes/state_node, kubernetes/state_pod, kubernetes/state_replicaset, kubernetes/system, kubernetes/volume, logstash/node, logstash/node_stats, memcached/stats, mongodb/collstats, mongodb/dbstats, mongodb/status, mysql/status, nginx/stubstatus, php_fpm/pool, postgresql/activity, postgresql/bgwriter, postgresql/database, prometheus/collector, prometheus/stats, rabbitmq/node, rabbitmq/queue, redis/info, redis/keyspace, system/core, system/cpu, system/diskio, system/filesystem, system/fsstat, system/load, system/memory, system/network, system/process, system/process_summary, system/raid, system/socket, system/uptime, uwsgi/status, vsphere/datastore, vsphere/host, vsphere/virtualmachine, zookeeper/mntr]]
2018-05-15T17:04:12.512-0500 INFO [monitoring] log/log.go:97 Starting metrics logging every 30s
2018-05-15T17:04:12.512-0500 INFO kibana/client.go:69 Kibana url: http://172.16.2.42:5601
2018-05-15T17:04:12.516-0500 DEBUG [dashboards] dashboards/kibana_loader.go:103 Initialize the Kibana 6.2.4 loader
2018-05-15T17:04:12.516-0500 DEBUG [dashboards] dashboards/kibana_loader.go:103 Kibana URL http://172.16.2.42:5601
2018-05-15T17:04:12.516-0500 DEBUG [dashboards] dashboards/kibana_loader.go:103 Importing directory /usr/share/metricbeat/bin/kibana/6
2018-05-15T17:04:12.518-0500 INFO [monitoring] log/log.go:132 Total non-zero metrics {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":20,"time":23},"total":{"ticks":30,"time":37,"value":30},"user":{"ticks":10,"time":14}},"info":{"ephemeral_id":"259949cd-984c-49a4-bba9-156d3e9e90b4","uptime":{"ms":38}},"memstats":{"gc_next":4194304,"memory_alloc":2341096,"memory_total":3958728,"rss":18051072}},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"logstash"},"pipeline":{"clients":0,"events":{"active":0}}},"system":{"cpu":{"cores":8},"load":{"1":1.57,"15":1.18,"5":1.36,"norm":{"1":0.1963,"15":0.1475,"5":0.17}}}}}}
2018-05-15T17:04:12.518-0500 INFO [monitoring] log/log.go:133 Uptime: 38.420796ms
2018-05-15T17:04:12.518-0500 INFO [monitoring] log/log.go:110 Stopping metrics logging.
2018-05-15T17:04:12.518-0500 ERROR instance/beat.go:667 Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing directory /usr/share/metricbeat/bin/kibana: No directory /usr/share/metricbeat/bin/kibana/6
Exiting: Error importing Kibana dashboards: fail to import the dashboards in Kibana: Error importing directory /usr/share/metricbeat/bin/kibana: No directory /usr/share/metricbeat/bin/kibana/6

```

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [May 16, 2018, 2:30pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/2 "2018-05-16T14:30:06Z")

</div>

@shanim Have you installed Metricbeat via a package(deb/rpm) or from the tar/gz?

---

<div class="post-metadata">

**Author:** ![shanim](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@shanim](https://discuss.elastic.co/u/shanim)\
**Post date:** [May 16, 2018, 2:51pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/3 "2018-05-16T14:51:57Z")

</div>

Metricbeat was installed with a package, i.e. the `.rpm`.

The setup works fine if we set `setup.dashboards.enabled: true` in `metricbeat.yml`, but we prefer running the CLI command only once rather than have metricbeat attempt a load every time it is started.

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [May 16, 2018, 3:03pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/4 "2018-05-16T15:03:01Z")

</div>

I think you are running the binary directly we are providing a shell shims that take care of some configuration.

Can you just execute `metricbeat -setup -e` ?

---

<div class="post-metadata">

**Author:** ![shanim](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@shanim](https://discuss.elastic.co/u/shanim)\
**Post date:** [May 16, 2018, 3:33pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/5 "2018-05-16T15:33:49Z")

</div>

We had tried that and it failed to run as it was unable to find the `metricbeat.yml` file

---

<div class="post-metadata">

**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\
**Post date:** [May 16, 2018, 3:44pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/6 "2018-05-16T15:44:38Z")

</div>

But adding `-c your config` to the metricbeat invocatio, should work?

---

<div class="post-metadata">

**Author:** ![shanim](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@shanim](https://discuss.elastic.co/u/shanim)\
**Post date:** [May 16, 2018, 3:49pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/7 "2018-05-16T15:49:34Z")

</div>

> [@shanim](#):
>
> [root@abcrd006 metricbeat]# ./bin/metricbeat -setup -e -c /etc/metricbeat/metricbeat.yml

The above output used `-c <config file location based on the rpm's SPEC file>`.

The metricbeat rpm installs metricbeat and puts the configuration file in `/etc/metricbeat` folder similar to the `elasticsearch.yml`, `kibana.yml` and `logstash.yml` that are stored in `/etc/<application>`

---

<div class="post-metadata">

**Author:** ![shanim](https://avatars.discourse-cdn.com/v4/letter/s/ce7236/32.png) [@shanim](https://discuss.elastic.co/u/shanim)\
**Post date:** [May 21, 2018, 5:29pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/8 "2018-05-21T17:29:02Z")

</div>

Any other thoughts on this issue?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 18, 2018, 5:29pm UTC](https://discuss.elastic.co/t/metricbeat-does-not-install-dashboards-when-running-setup/132006/9 "2018-06-18T17:29:10Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
