mapping conflict under Kibana / stack management / index patterns / *:so-* #4912
Replies: 1 comment 4 replies
-
Hey @jchenturbo, would you be able to find which fields have conflicts by looking in the I found that |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
While working on our standalone instance of SO 2.3.61.. i noticed this error under Kibana / stack management / index patterns / :so-
Time field: '@timestamp'
Mapping conflict
A field is defined as several types (string, integer, etc) across the indices that match this pattern. You may still be able to use these conflict fields in parts of Kibana, but they will be unavailable for functions that require Kibana to know their type. Correcting this issue will require reindexing your data.
I wasn't sure if we caused it so we deployed another instance fresh from the ISO and see the same warning..
Is this something to be concerned about? how can we fix it?
Beta Was this translation helpful? Give feedback.
All reactions