Metricbeat does not install dashboards when running setup

Elastic Stack Beats
1

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.

[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
2

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

3

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.

4

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 ?

5

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

6

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

7

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>

8

Any other thoughts on this issue?

9

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