You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
KB currently reads the field list from the index. An index can contain multiple Types
From the ES docs:
"...type is defined for documents that have a set of common fields"
When you have many different types within the same index the dropdowns can get rather confusing if fieldnames are not consistent across types.
It is not possible to define an index pattern that includes the Type that you are interested in - the UI reports it as an invalid index pattern.
Couple of suggestions
Support an optional Type when defining an index pattern
Let the user filter the field list by Type when creating visualisations
We generally don't recommend people use types, rather just pick an arbitrary field and call it type. Types can get messy and there's a big refactoring of them coming in ES 2.0 that will likely be painful for many logging users.
We're working to improve the select box, but grouping by type isnt likely to be the way we do it: #2130
KB currently reads the field list from the index. An index can contain multiple Types
From the ES docs:
"...type is defined for documents that have a set of common fields"
When you have many different types within the same index the dropdowns can get rather confusing if fieldnames are not consistent across types.
It is not possible to define an index pattern that includes the Type that you are interested in - the UI reports it as an invalid index pattern.
Couple of suggestions
This is somewhat related to #1540
The text was updated successfully, but these errors were encountered: