# Exiting: resource 'metricbeat-7.4.2' exists, but it is not an alias

**URL:** https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685
**Category:** Beats
**Tags:** metricbeat
**Created:** [November 5, 2019, 10:48pm UTC](https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685 "2019-11-05T22:48:23Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![dnorth98](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dnorth98/32/54823_2.png) [@dnorth98](https://discuss.elastic.co/u/dnorth98)
#### Post date: [November 6, 2019, 3:24pm UTC](https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685/3 "2019-11-06T15:24:56Z")

</div>

I managed to find a way around this in case anyone else is interested. Here's what I had to do:

- Stop new index auto-creation

- Deleted the `metricbeat-7.4.0` index (I can afford to lose this data)

- Created a new `metricbeat-7.4.0-2019-11-06` index and assign it the alias

`PUT /metricbeat-7.4.0-2019-11-06`

```auto
{
    "actions" : [
        { "add" : { "index" : "metricbeat-7.4.0-2019.11.06-000001", "alias" : "metricbeat-7.4.0", "is_write_index" : "true" }
           }
    ]
}

```

- Re-enable auto-index creation (remove from user config)

The index I created quickly rolled over but I'm all good now. None of the metricbeat clients had to be touched to get back to a working state. Hoorah!

Cheers

Dave

---

_[View the full topic](https://discuss.elastic.co/t/exiting-resource-metricbeat-7-4-2-exists-but-it-is-not-an-alias/206685)._