-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text aggregations are failing #5
Comments
If you are getting these issues is probably that you don't have the type field as keyword, all host, source, type should be keyword |
We're using the default logstash template which analyzes the base field and uses .keyword for the keyword fields, and I'd prefer to keep using this scheme. Not a problem, I can just fork and update it for my environment. |
@dbason any chance you'd be willing to share your fork? I'm running into this same issue (type is text and have type.keyword), but I cannot seem to figure out how to patch kibana-logbrowser to use type.keyword instead. Thanks! |
@sunomie I actually didn't pursue this sorry. We've ended up using the logtrail plugin instead - https://github.com/sivasamyk/logtrail |
When generating the list of hosts I get the following error in the Kibana logs:
"Fielddata is disabled on text fields by default. Set fielddata=true on [type] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory"
Should the source, host, and type aggregations be using the .raw or .keyword fields?
The text was updated successfully, but these errors were encountered: