Unable to ceate new index pattern in kibana

Hi,
i'm using elastic stack fpr several years.
I've been watching the problem since version 5.xx and up to 7.13.2

After some time of usage your're unable to crate new index patterns in kibana.
The "create index pattern" wizzard works fine for the first step.
In step 2 you'll get :"
The indices which match this index pattern don't contain any time fields.", for any pattern you chose.
Yes, in every index is a valid "@timestamp" field.

please help
ulrich

Hi ulrich, can you share the mapping for one of your chosen indexes?

Hi Nich, here we go:

{
  "mappings": {
    "_doc": {
      "dynamic": "true",
      "_meta": {},
      "_source": {
        "includes": [],
        "excludes": []
      },
      "dynamic_date_formats": [
        "strict_date_optional_time",
        "yyyy/MM/dd HH:mm:ss Z||yyyy/MM/dd Z"
      ],
      "dynamic_templates": [
        {
          "strings": {
            "match_mapping_type": "string",
            "mapping": {
              "norms": false,
              "type": "keyword"
            }
          }
        }
      ],
      "date_detection": true,
      "numeric_detection": false,
      "properties": {
        "@timestamp": {
          "type": "date",
          "format": "strict_date_optional_time"
        },
        "clientiphash": {
          "type": "keyword"
        },
        "cpcode": {
          "type": "keyword"
        },
        "duration": {
          "type": "float"
        },
        "elastic": {
          "type": "keyword"
        },
        "filehash": {
          "type": "keyword"
        },
        "filename": {
          "type": "keyword"
        },
        "geoip": {
          "properties": {
            "location": {
              "type": "geo_point"
            }
          }
        },
        "index": {
          "type": "keyword"
        },
        "lines": {
          "type": "long"
        },
        "linesps": {
          "type": "float"
        },
        "processed": {
          "type": "date",
          "format": "strict_date_optional_time"
        }
      }
    }
  }
}

I hat this issue many times.
The only working resolution is to stop kibana, configure a new index for kibana and start again.

ulrich

Manage