-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Kibana messing graphs with fields containing '/' and '.' #6203
Comments
It's an analysed field - click the yellow warning triangle in your screenshot |
How about mapping for that field set to not analyse. ( you will need to { "type": "string", "index": "not_analyzed" } Sent from Gmail Mobile |
But shouldn't Logstash do this, while creating the new index?? |
As noted by the comments above, this is not a kibana issue. |
If you're using default logstash settings there should be a request.raw field |
* fixes sorting to what it was in 7.6.1 * removes sortable=true from non-sortable columns, fixes naming of sortable column field from activate to enabled to match the field eui expects to sort on, fixes react render warning due to resetting tableRef's current field during a render
* fixes sorting to what it was in 7.6.1 * removes sortable=true from non-sortable columns, fixes naming of sortable column field from activate to enabled to match the field eui expects to sort on, fixes react render warning due to resetting tableRef's current field during a render Co-authored-by: Elastic Machine <[email protected]>
There is a strange bug on Kibana.
On an environment with Kibana 4.4.0, ES 2.2.0 and so, I'm extracting some Apache Logs using Logstash (with the "COMBINEDAPACHE" grok pattern) directly to ElasticSearch.
While using Kibana, doing a quick discover on the field, the data is returned as expected (as on the following screenshot):
But when doing a simple graph with the values (as a Pie Chart), Kibana understands the values separated by '.' or '/' as different values, and generates a graph with each of those values as a different request:
Thanks
The text was updated successfully, but these errors were encountered: