Skip to content
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

Closed
rikatz opened this issue Feb 11, 2016 · 5 comments
Closed

Kibana messing graphs with fields containing '/' and '.' #6203

rikatz opened this issue Feb 11, 2016 · 5 comments

Comments

@rikatz
Copy link

rikatz commented Feb 11, 2016

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):

quickcount-request

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:

request-piechart

Thanks

@jimmyjones2
Copy link
Contributor

It's an analysed field - click the yellow warning triangle in your screenshot

@marcinkubica
Copy link

How about mapping for that field set to not analyse. ( you will need to
reindex your data )

{ "type": "string", "index": "not_analyzed" }

Sent from Gmail Mobile

@rikatz
Copy link
Author

rikatz commented Feb 12, 2016

But shouldn't Logstash do this, while creating the new index??

@rashidkpc
Copy link
Contributor

As noted by the comments above, this is not a kibana issue.

@jimmyjones2
Copy link
Contributor

If you're using default logstash settings there should be a request.raw field

dhurley14 added a commit that referenced this issue Apr 2, 2020
* 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
dhurley14 added a commit that referenced this issue Apr 2, 2020
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants