### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 25, 2020, 12:19pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/1 "2020-02-25T12:19:32Z")
Hi,
I am unable to setup Metricbeat dashboards.
I'm trying the following:
```
metricbeat setup --dashboards
```
And getting this error:
```
Loading dashboards (Kibana must be running and reachable)
Exiting: error connecting to Kibana: fail to get the Kibana version: HTTP GET request to https://xxxxx.es.io:9243/api/status fails: . Response: {"error":"Incorrect HTTP method for uri [/api/status] and method [GET], allowed: [POST]","status":405}.
```
When i try the same with auditbeat it workds fine.
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 25, 2020, 9:52pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/2 "2020-02-25T21:52:08Z")
Hi @tristan1 🙂
What's your elasticsearch and kibana version, please?
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 26, 2020, 7:37am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/3 "2020-02-26T07:37:24Z")
Im using version 7.6 on centos
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 28, 2020, 6:47am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/4 "2020-02-28T06:47:41Z")
Both of them latest version
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 28, 2020, 10:58am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/5 "2020-02-28T10:58:26Z")
it sounds familiar to me that it's a version issue, corrected when using kibana + elastic + metricbeat with version \>7.5
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 28, 2020, 11:01am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/6 "2020-02-28T11:01:35Z")
Kibana Elastic and Metricbeat all running the newest version. Its strange that of all beats only metricbeat is not working with creating dashboards.
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 28, 2020, 11:12am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/7 "2020-02-28T11:12:01Z")
We don't have issues reported about this so I'm lean to think it's something small in your env:
> [@tristan1](#):
>
> [https://xxxxx.es.io:9243/api/status](https://xxxxx.es.io:9243/api/status)
Where is this deployed? AWS?
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 28, 2020, 12:01pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/8 "2020-02-28T12:01:33Z")
We are using elastic ece.
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 28, 2020, 1:39pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/9 "2020-02-28T13:39:14Z")
Can you paste your metricbeat configuration? I think you might have configured kibana in auditbeat config but not in metricbeat?
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 28, 2020, 1:42pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/10 "2020-02-28T13:42:48Z")
```auto
###################### Metricbeat Configuration Example #######################
# This file is an example configuration file highlighting only the most common
# options. The metricbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/metricbeat/index.html
#========================== Modules configuration ============================
metricbeat.config.modules:
# Glob pattern for configuration loading
path: ${path.config}/modules.d/*.yml
# Set to true to enable config reloading
reload.enabled: false
# Period on which files under path should be checked for changes
#reload.period: 10s
#==================== Elasticsearch template setting ==========================
setup.template.settings:
index.number_of_shards: 1
index.codec: best_compression
#_source.enabled: false
#================================ General =====================================
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: true
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
#============================== Kibana =====================================
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:
# Kibana Host
# Scheme and port can be left out and will be set to the default (http and 5601)
# In case you specify and additional path, the scheme is required: http://localhost:5601/path
# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
host: "https://XXXXXX.ip.es.io:9243"
ssl.verification_mode: none
# Kibana Space ID
# ID of the Kibana Space into which the dashboards should be loaded. By default,
# the Default Space will be used.
#space.id:
#============================= Elastic Cloud ==================================
# These settings simplify using Metricbeat with the Elastic Cloud (https://cloud.elastic.co/).
# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:
# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `:`.
#cloud.auth:
#================================ Outputs =====================================
# Configure what output to use when sending the data collected by the beat.
#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
# Array of hosts to connect to.
hosts: ["http://XXXXXX.ip.es.io:9200/"]
certificate_authorities: none
# Protocol - either `http` (default) or `https`.
#protocol: "https"
# Authentication credentials - either API key or username/password.
#api_key: "id:api_key"
#username: "elastic"
#password: "changeme"
username: "xxxxx"
password: "xxxxx"
#----------------------------- Logstash output --------------------------------
#output.logstash:
# The Logstash hosts
#hosts: ["localhost:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications
#ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
# Certificate for SSL client authentication
#ssl.certificate: "/etc/pki/client/cert.pem"
# Client Certificate Key
#ssl.key: "/etc/pki/client/cert.key"
#================================ Processors =====================================
# Configure processors to enhance or manipulate events generated by the beat.
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~
- add_docker_metadata: ~
- add_kubernetes_metadata: ~
#================================ Logging =====================================
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
logging.level: error
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]
#============================== X-Pack Monitoring ===============================
# metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.
# Set to true to enable the monitoring reporter.
#monitoring.enabled: false
# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Metricbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:
#================================= Migration ==================================
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
```
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 28, 2020, 1:45pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/11 "2020-02-28T13:45:54Z")
Can you change the port of the Kibana URL to 5601 and check? I can also see that, somehow, you are using `https` in kibana but not in Elasticsearch urls
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [February 28, 2020, 2:04pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/12 "2020-02-28T14:04:11Z")
Kibana is not using a default port. Beside that i used the same config in auditbeat and i was also able to load the dashboards.
"can also see that, somehow, you are using `https` in kibana but not in Elasticsearch urls)"
Also this configuration i'm using in auditbeat.
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [February 28, 2020, 2:32pm UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/13 "2020-02-28T14:32:03Z")
I'm sorry if I'm not being very helpful but, somehow, there must be something different. The code which loads configuration from `yml` files and load dashboards into Kibana is shared between all beats.
In fact, you could simply move the `json` files inside `metricbeat/module/**/_meta/kibana/7/dashboard/*.json` to `auditbeat/module/auditd/_meta/kibana/7/dashboard` (for example) to load the module you are looking for
---
### Author:  [@tristan1](https://discuss.elastic.co/u/tristan1)
#### Post date: [March 3, 2020, 7:10am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/14 "2020-03-03T07:10:54Z")
Hi Mario,
I have fixed the issue. The destination adress was not correct. 🥺
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 31, 2020, 7:10am UTC](https://discuss.elastic.co/t/unable-to-setup-metricbeat-dashboards/220852/15 "2020-03-31T07:10:59Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.