# Multiple metricbeat index for each host
**URL:** https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674
**Category:** Beats
**Tags:** metricbeat
**Created:** [January 30, 2018, 5:14pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674 "2018-01-30T17:14:21Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@arun\_prasath1](https://discuss.elastic.co/u/arun_prasath1)
#### Post date: [January 30, 2018, 5:14pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/1 "2018-01-30T17:14:21Z")
Currently i am sending metricbeat data from all the server directly to elastichost:9200. This way metricbeat data from all the server sends data to single metricbeat-dataIs it possible to create separate index for metricbeat data from each server. Current metricbeat configuration is like below.
metricbeat.yml:
metricbeat.modules:
#------------------------------- System Module -------------------------------
- module: system
metricsets:
- cpu
- load
- filesystem
- fsstat
- memory
- network
- process
enabled: true
period: 10s
processes: ['.\*']
output.elasticsearch:
hosts: ["elastichost:9200"]
For example, I looking for separate metricbeat index for each host.
metricbeat-host1-dd-mm-yy
metricbeat-host2-dd-mm-yy
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [January 30, 2018, 5:30pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/2 "2018-01-30T17:30:15Z")
You can change the [index` setting](https://www.elastic.co/guide/en/beats/metricbeat/current/elasticsearch-output.html#index-option-es).
E.g.
```auto
output.elasticsearch:
index: 'metricbeat-%{[beat.version]}-%{[beat.name]}-%{+yyyy.MM.dd}'
```
This way the index-name is still versioned by the beat version (required to the template mapping still to be applied). I'm using `beat.name` here. The hostname is stored in `beat.hostname`. The `beat.name` is the hostname by default, but can be reconfigured using the global `name` setting in beats.
---
### Author:  [@arun\_prasath1](https://discuss.elastic.co/u/arun_prasath1)
#### Post date: [January 30, 2018, 5:35pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/3 "2018-01-30T17:35:08Z")
Nice and simple. I will try this and let you know. Thanks Steffens.
---
### Author:  [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [January 30, 2018, 5:53pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/4 "2018-01-30T17:53:09Z")
Before making this change, be aware that having a large number of small indices can be very inefficient.
---
### Author:  [@arun\_prasath1](https://discuss.elastic.co/u/arun_prasath1)
#### Post date: [January 31, 2018, 12:42pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/5 "2018-01-31T12:42:03Z")
This is what i was looking for. Initially i thought to send to logstash and create separate index using logstash output. But this creates directly in ES.
@Christian_Dahlqvist - I am using this option for one or two servers to monitor and retain the index for a month.
Thanks team for your help.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 28, 2018, 12:42pm UTC](https://discuss.elastic.co/t/multiple-metricbeat-index-for-each-host/117674/6 "2018-02-28T12:42:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.