# The indices which match this index pattern don't contain any time fields

**URL:** <https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403>\
**Category:** Kibana\
**Created:** [January 4, 2022, 5:38am UTC](https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403 "2022-01-04T05:38:30Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![damienhaynes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/damienhaynes/32/99782_2.png) [@damienhaynes](https://discuss.elastic.co/u/damienhaynes)\
**Post date:** [January 6, 2022, 9:23pm UTC](https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403/21 "2022-01-06T21:23:05Z")

</div>

Thanks for your help so far @can.ozdemir.

We're currently using Kibana 7.9.3, I can see there are two upgrade paths available from the admin page (7.16.2 and 7.15.2), do you think upgrading might help?

Right now I think there is something fundamentally wrong, we have two other index patterns, both of which have mapping conflicts e.g.

 ![index_pattern_conflicts](https://us1.discourse-cdn.com/elastic/original/3X/9/a/9aa2c5edbcfcee56b2bd190485d8ebfff9fbfb52.jpeg)

These conflicts have been resolved a long time ago, but when I click refresh, no changes occur, I can see similar errors as above when I view the F12 developer mode e.g.:

```auto
GET https://8108e04d2b7a47a98da904a3323f33d4.australiaeast.azure.elastic-cloud.com:9243/api/index_patterns/_fields_for_wildcard?pattern=aqueduct-staging-*&meta_fields=_source 400

Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'get')
    at IndexPattern.addError [as onError] (core.entry.js:84)
    at data.plugin.js:14

```

When I click edit on one of these fields, I can see the reason for conflicts, but they are referring to index logs that have been cleaned up a long time ago (we only hold 14 days):

 ![invalid_log_indices](https://us1.discourse-cdn.com/elastic/original/3X/d/8/d8459e318dfc76940a230fa7992608a579ed2671.jpeg)

Anyway, this is the main reason why I started this thread because on our development index I was trying to fix the refresh issue, this lead me to delete the index and start again but now get stuck creating the index pattern ☹

The only thing I can think of, is to do an upgrade as I want to fix these mapping conflicts on existing index patterns and also re-create my dev index pattern.

---

<div class="post-metadata">

**Author:** ![damienhaynes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/damienhaynes/32/99782_2.png) [@damienhaynes](https://discuss.elastic.co/u/damienhaynes)\
**Post date:** [January 10, 2022, 6:41am UTC](https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403/22 "2022-01-10T06:41:07Z")

</div>

I created a new account (free trial) with elastic v7.16.2, I didn't run into any issues.

Ideally, I do not want to upgrade in case of loss, but I do not know what else to try. I can very well upgrade but may still have the same issues.

---

<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:** [February 7, 2022, 6:41am UTC](https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403/23 "2022-02-07T06:41:23Z")

</div>

Closed on February 7, 2022, 6:41am UTC

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

[Previous page](https://discuss.elastic.co/t/the-indices-which-match-this-index-pattern-dont-contain-any-time-fields/293403.md?page=1)