# Index\_Pattern set to metricbeat-\* on sample dashboards

**URL:** <https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 7, 2018, 5:12pm UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889 "2018-02-07T17:12:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![andyliddle](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@andyliddle](https://discuss.elastic.co/u/andyliddle)\
**Post date:** [February 7, 2018, 5:12pm UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889/1 "2018-02-07T17:12:14Z")

</div>

Hi,

Not sure if this is limited to metricbeat but,

I noticed that in 6.2 that the index\_pattern on the default dashboards is set to "index\_pattern":"metricbeat-_" when in the version 6.1.3 is was set to "index\_pattern":"_".

Is there anyway i can override this in config or do i need to manually change the templates between adding them to elesticsearch?

Currently I plan to use a custom index pattern to store all beats:

```auto
setup.template.name: "dev-metricbeat-%{[beat.version]}"
setup.template.pattern: "dev-*"
setup.dashboards.index: "dev-*"

```

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [February 8, 2018, 11:34pm UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889/2 "2018-02-08T23:34:23Z")

</div>

When importing the dashboards, the index-pattern to be used by the dashboards should be defined by [setup.dashboards.index](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-dashboards.html#_literal_setup_dashboards_index_literal).

If you use `setup.dashboard.index`, is the index-pattern set as you would expect? If not, which Elasticsearch and Kibana versions are you using?

Btw. you should version the template pattern as well. With the template name versioned, you might end up with multiple templates matching a new index name, potentially giving you weird problems/errors on updates.

---

<div class="post-metadata">

**Author:** ![andyliddle](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@andyliddle](https://discuss.elastic.co/u/andyliddle)\
**Post date:** [February 9, 2018, 10:55am UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889/3 "2018-02-09T10:55:16Z")

</div>

no it doesn't seem to be replacing whats has been set in the template for example when importing the metricbeat-6.2.0-windows-x86\_64\kibana\6\dashboard\Metricbeat-system-overview.json.

.\metricbeat setup --dashboards -E output.logstash.enabled=false -E 'output.elasticsearch.index=dev-%{+yyyy-MM-dd}' -E 'output.elasticsearch.hosts=["[elastic1.domain.com:9200](http://elastic1.domain.com:9200)"]'

I've using 6.2.0 for elasticsearch, kibana, logstash.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [February 9, 2018, 1:46pm UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889/4 "2018-02-09T13:46:11Z")

</div>

Sounds like you are hitting this bug: [https://github.com/elastic/beats/issues/4345](https://github.com/elastic/beats/issues/4345)

Can you comment in this ticket with configs and command, so it's clear the problem is not solved in 6.x?

---

<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:** [March 9, 2018, 1:46pm UTC](https://discuss.elastic.co/t/index-pattern-set-to-metricbeat-on-sample-dashboards/118889/5 "2018-03-09T13:46:15Z")

</div>

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