# Unable to config filebeat with kibana, loaded dashboard Exiting 1 ERROR : error loading config file, invalid config, yaml, did not find expected '-' indicator

**URL:** <https://discuss.elastic.co/t/unable-to-config-filebeat-with-kibana-loaded-dashboard-exiting-1-error-error-loading-config-file-invalid-config-yaml-did-not-find-expected-indicator/146426>\
**Category:** Kibana\
**Created:** [August 28, 2018, 9:46pm UTC](https://discuss.elastic.co/t/unable-to-config-filebeat-with-kibana-loaded-dashboard-exiting-1-error-error-loading-config-file-invalid-config-yaml-did-not-find-expected-indicator/146426 "2018-08-28T21:46:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anwarshahtarn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anwarshahtarn/32/34821_2.png) [@anwarshahtarn](https://discuss.elastic.co/u/anwarshahtarn)\
**Post date:** [August 28, 2018, 9:46pm UTC](https://discuss.elastic.co/t/unable-to-config-filebeat-with-kibana-loaded-dashboard-exiting-1-error-error-loading-config-file-invalid-config-yaml-did-not-find-expected-indicator/146426/1 "2018-08-28T21:46:20Z")

</div>

```
    Here is my filebeat.yaml config file

```

###################### Filebeat Configuration Example #########################

# This file is an example configuration file highlighting only the most common

# options. The filebeat.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/filebeat/index.html](https://www.elastic.co/guide/en/beats/filebeat/index.html)

# For more available modules and options, please see the filebeat.reference.yml sample

# configuration file.

#=========================== Filebeat inputs =============================

filebeat.inputs:

# Each - is an input. Most options can be set at the input level, so

# you can use different inputs for various configurations.

# Below are the input specific configurations.

- type: log

#============================= Filebeat modules ===============================

filebeat.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: 3  
#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` CLI flag or the `setup` command.

#setup.dashboards.enabled: false

# 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](http://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](http://localhost:5601/path)

# IPv6 addresses should always be defined as: https://[2001:db8::1]:5601

```
host: "localhost:5601"

```

#================================ 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: ["localhost:9200"]

# Optional protocol and basic auth credentials.

#protocol: "https"  
#username: "elastic"  
#password: "changeme"

#----------------------------- 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"

#================================ Logging =====================================

# Sets log level. The default log level is info.

# Available log levels are: error, warning, info, debug

#logging.level: debug

# 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: ["\*"]

#============================== Xpack Monitoring ===============================

# filebeat 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.

#xpack.monitoring.enabled: false

# Uncomment to send the metrics to Elasticsearch. Most settings from the

# Elasticsearch output are accepted here as well. Any setting that is not set is

# automatically inherited from the Elasticsearch output configuration, so if you

# have the Elasticsearch output configured, you can simply uncomment the

# following line.

#xpack.monitoring.elasticsearch:

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 28, 2018, 10:04pm UTC](https://discuss.elastic.co/t/unable-to-config-filebeat-with-kibana-loaded-dashboard-exiting-1-error-error-loading-config-file-invalid-config-yaml-did-not-find-expected-indicator/146426/2 "2018-08-28T22:04:46Z")

</div>

Please edit your post and use the `</>`, or markdown backticks, to format things as code. It's very difficult to provide assistance without this.

---

<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:** [September 25, 2018, 10:08pm UTC](https://discuss.elastic.co/t/unable-to-config-filebeat-with-kibana-loaded-dashboard-exiting-1-error-error-loading-config-file-invalid-config-yaml-did-not-find-expected-indicator/146426/3 "2018-09-25T22:08:11Z")

</div>

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