# Heartbeat 7 configuration issues: monitors & index name

**URL:** <https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [April 29, 2019, 1:19pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938 "2019-04-29T13:19:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc-Antoine\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc-antoine_j/32/39687_2.png) [@Marc-Antoine\_J](https://discuss.elastic.co/u/Marc-Antoine_J)\
**Post date:** [April 29, 2019, 1:19pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938/1 "2019-04-29T13:19:21Z")

</div>

Hi all,

I upgraded my full stack to 7.0 lately. This morning I noticed no heartbeat docs were coming in my elasticsearch. I started heartbeat with debug logs then I noticed it was not loading any monitors config files even if I have all my monitors in /etc/heartbeat/monitors.d/ as monitor1.yml monitor2.yml monitor3.yml. File permissions are right. I then changed the "path" config from:  
`path: ${path.config}/monitors.d/*.yml`  
to  
`path: /etc/heartbeat/monitors.d/*.yml`  
Now the monitors are detected and works fine. Weird?

Next even if I had configured my own template settings it created a template with the default options provided like if brand new heartbeat.yml config file was provided. I mean even if I named the template heartbeat-local it named it heartbeat-7.0.0. I also set my elasticsearch output to set the index name to heartbeat-%{+yyyy.MM} and it created the index as:  
`heartbeat-7.0.0-2019.04.29-000001`  
Now I agree I should include the version name in my index so I made simple changes on the index pattern and template name but I want those docs to be in monthly created index instead of daily. And I can't find a workaround to have the configuration file read correctly my index name pattern...

My configuration file is correctly loaded by heartbeat since i can actually switch the log levels and change the reload.enabled config successfully.

Here's my heartbeat.yml:

```
heartbeat.config.monitors:
  #path: ${path.config}/monitors.d/*.yml
  path: /etc/heartbeat/monitors.d/*.yml
  reload.enabled: true
  reload.period: 5s
  
name: local-heartbeat-monitor

setup.kibana:
  host: "<ip>:<port>"
  
output.elasticsearch:
  hosts: ["<ip>:<port>"]
  index: "heartbeat-%{[agent.version]}-%{+yyyy.MM}"
  
setup.template.name: "heartbeat-%{[agent.version]}"
setup.template.pattern: "heartbeat-%{[agent.version]}-*"
setup.template.overwrite: false
setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~

logging.level: info
logging.to_files: true
logging.files:
  path: "/var/log/heartbeat/logs"
  name: heartbeat.log
  keepfiles: 7
  
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch:

```

Thanks

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [April 29, 2019, 3:23pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938/2 "2019-04-29T15:23:59Z")

</div>

Hey, beats 7 uses ILM (Index Lifecycle Management) instead of time series indices. This is a much more powerful way of managing index naming. If you'd like to change the naming patterns I'd recommend changing the ILM policy. See [https://www.elastic.co/blog/beats-7-0-0-released#ilm](https://www.elastic.co/blog/beats-7-0-0-released#ilm) for more detail.

---

<div class="post-metadata">

**Author:** ![Marc-Antoine\_J](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marc-antoine_j/32/39687_2.png) [@Marc-Antoine\_J](https://discuss.elastic.co/u/Marc-Antoine_J)\
**Post date:** [April 29, 2019, 3:59pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938/3 "2019-04-29T15:59:32Z")

</div>

Thanks @Andrew_Cholakian1 for the ILM details. I'll be happy to work with this new API as it brings nice functionalities. I actually started to work with it since 6.6.

But i'm wondering something... Does this means that the beats indexes will always be using default index naming? We cannot customize it anymore? I only tried to remove the day and keep only year and month so it creates monthly indexes instead of daily. I don't mind the extra 000001 or the lifecycling of my indexes. As I can see the ILM is not managing the index name itself, only the alias it's using and the other ILM details not about the naming itself.

Thanks,

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [April 29, 2019, 7:05pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938/4 "2019-04-29T19:05:24Z")

</div>

Have you seen the ILM config options here? [https://www.elastic.co/guide/en/beats/heartbeat/current/ilm.html](https://www.elastic.co/guide/en/beats/heartbeat/current/ilm.html)

---

<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:** [May 27, 2019, 7:05pm UTC](https://discuss.elastic.co/t/heartbeat-7-configuration-issues-monitors-index-name/178938/5 "2019-05-27T19:05:24Z")

</div>

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