Loading filebeat default dashboard while using different index name

[gazolle (Alex)]

Good day,

I am seeking assistance on configuring Kibana to use Filebeats default (pre-made) dashboard, running on version 7.1.1.

From the documentation I came across (Steps 4-5) it should be feasible. I modified the filebeat.yml to include the following lines:

output.elasticsearch.index: "demo-001-%{+yyyy.MM.dd}"
setup.template.name: "demo-001"
setup.template.pattern: "demo-001-*"

..Then run 'filebeat setup' command, once completed. I can see the dashboard and visualization. Great! However when I want to view a dashboard I get the error along the lines of Could not locate that index-pattern (id: demo-001-*), click here to re-create it and I am not too sure why at this point, as my index-pattern is defined on Kibana; and not sure where to look at this point. I was not able to pinpoint a solutions on the forum.

Thank you in advance for your assistance.

[shaunak (Shaunak Kashyap)]

Would you mind posting your complete filebeat.yml? Please be sure to redact any sensitive information before posting.

Also, if you go to Kibana > Management > Index Patterns, do you see your index pattern defined there?

Thanks,

Shaunak

[gazolle (Alex)]

Not at all @shaunak. First of all, please excuse me for the delay.

As requested, below is the filebeat.yml config:
#=========================== Filebeat inputs =============================

filebeat.inputs:
- type: log
# Change to true to enable this input configuration.
enabled: true
# Paths that should be crawled and fetched. Glob based paths.
paths:
- /var/log/*.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: 1
setup.template.name: "demo-001"
setup.template.pattern: "demo-001-*"

#================================ 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: ["server-a"]

#============================== 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 thesetupcommand.
#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
# 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://10.60.11.16:5601"
ssl.certificate_authorities: ["/etc/filebeat/certs/ca.crt"]
ssl.certificate: "/etc/filebeat/certs/webgoat.crt"
ssl.key: "/etc/filebeat/certs/webgoat.key"

#================================ Outputs =====================================
#-------------------------- Elasticsearch output ------------------------------

output.elasticsearch:
# Array of hosts to connect to.
hosts: ["https://10.60.11.16:9200","https://10.60.11.17:9200","https://10.60.11.18:9200"]
# Enabled ilm (beta) to use index lifecycle management instead daily indices.
#ilm.enabled: true
# Optional protocol and basic auth credentials.
protocol: "https"
username: "elastic"
password: "abc1234"
index: "demo-001-%{+yyyy.MM.dd}"
ssl.certificate_authorities: ["/etc/filebeat/certs/ca.crt"]
ssl.certificate: "/etc/filebeat/certs/webgoat.crt"
ssl.key: "/etc/filebeat/certs/webgoat.key"

#----------------------------- Logstash output --------------------------------

#output.logstash:
# The Logstash hosts
#hosts: ["https://10.60.11.23:5044"]
# Optional SSL. By default is off.
# List of root certificates for HTTPS server verifications

#================================ Processors =====================================

# Configure processors to enhance or manipulate events generated by the beat.
processors:
- add_host_metadata: ~
- add_cloud_metadata: ~

#================================ 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:

#================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

Yes, I can see the index-pattern demo-001 on Kibana. I would like to mentionned that I am sending events via Logstash (The reason why the lines are commented out, is because I recently tried the filebeat setup --dashboards command. My index pattern was created manually by me, and not pushed via filebeat.