Mapping conflict between two indexes of different versions of metricbeat

Elastic Stack Elasticsearch
1

Hi, I have two metricbeats with diferent versions pointing to the same elasticsearch, the difference between their mapping is causing me problems when I try to use the control visualization in kibana.

image

if i choose to use the field psql.name.keyword only the values of the index metricbeat-7.17.9 appears in the dropdown.

if i choose to use the field psql.name only the values of the index metricbeat-7.17.5 appears in the dropdown.

These are the mapping of the indexes:

{
  "metricbeat-7.17.9" : {
    "mappings" : {
      "psql.name" : {
        "full_name" : "psql.name",
        "mapping" : {
          "name" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          }
        }
      }
    }
  }
}

  "metricbeat-7.17.5" : {
    "mappings" : {
      "psql.name" : {
        "full_name" : "psql.name",
        "mapping" : {
          "name" : {
            "type" : "keyword",
            "ignore_above" : 1024
          }
        }
      }
    }
  }

Any ideas on how to solve this?

Thanks!

2

Did you run filebeat setup -e for the 7.17.9 version before you started the feed, that looks like a default mapping not the template mapping..

3

Also can you update all instances to the same version?

4

Hi, No, I did not. is there a way to solve this?

5

I think I can, but I will have to reindex the data? how to make shure that this custom field has the same mapping than the 7.17.5 when reindexing?

6

You should run setup and that should load the correct template and then reindex.

7

Keeping 7.17.9 or 7.17.5?

8

In short you always need to run setup for the version you are upgrading to... At least once.

So apologies typo run set for the new 7.17.9

9

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