# Getting metricbeat error on 7.14 v

**URL:** <https://discuss.elastic.co/t/getting-metricbeat-error-on-7-14-v/282272>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 23, 2021, 9:11pm UTC](https://discuss.elastic.co/t/getting-metricbeat-error-on-7-14-v/282272 "2021-08-23T21:11:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![cool999](https://avatars.discourse-cdn.com/v4/letter/c/d26b3c/32.png) [@cool999](https://discuss.elastic.co/u/cool999)\
**Post date:** [August 24, 2021, 12:12pm UTC](https://discuss.elastic.co/t/getting-metricbeat-error-on-7-14-v/282272/4 "2021-08-24T12:12:42Z")

</div>

Hi @stephenb,

Sorry to include you directly.

Below is the open case having similar error.

> [@Index lifecycle error on metricbeat and heartbeat](https://discuss.elastic.co/t/index-lifecycle-error-on-metricbeat-and-heartbeat/280715/3):
>
> Run the following in Kibana / Dev Tools and report back GET metricbeat-7.4.0/\_alias

only difference is that was completely on `v7.4.0` but here I am installing all components with `v7.14.0` and changing any ref of `7.4` to `7.14` in our automation tool.

Output of `GET metricbeat-7.4.0/_alias` as requested there.

```auto
#! this request accesses aliases with names reserved for system indices: [.kibana_task_manager, .security, .kibana_task_manager_7.14.0, .kibana, .kibana_7.14.0], but in a future major version, direct access to system indices and their aliases will not be allowed
{
  "metricbeat-7.4.0-2021.08.23-000001" : {
    "aliases" : {
      "metricbeat-7.4.0" : {
        "is_write_index" : true
      }
    }
  }
}

```

Its showing index with 7.4 even if 7.14 v is installed.

```auto
[root@ip-10-10-10-242 ~]# rpm -qa |grep metricbeat
metricbeat-7.14.0-1.x86_64

[root@ip-10-0-1-142 ~]# rpm -qa |grep heartbeat
heartbeat-elastic-7.14.0-1.x86_64
[root@ip-10-10-10-242 ~]# 

```

Thanks,

---

_[View the full topic](https://discuss.elastic.co/t/getting-metricbeat-error-on-7-14-v/282272)._