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

PIE chart splits the values before making the chart #231

Closed
nielsbasjes opened this issue Jul 18, 2013 · 6 comments · May be fixed by enterstudio/kibana#83
Closed

PIE chart splits the values before making the chart #231

nielsbasjes opened this issue Jul 18, 2013 · 6 comments · May be fixed by enterstudio/kibana#83

Comments

@nielsbasjes
Copy link

If the values you want to show in a pie chart contain spaces then those values are split before they are placed into the pie chart. This makes those pie charts effectively useless in those situations.

As an example: If you put the user agent string from a weblog into a PIE chart then you get the screenshot below.

kibanapiechart

If I filter in one specific useragent
"Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"
I get this:
kibanapiechart2

@nielsbasjes
Copy link
Author

Note: I'm using git commit id c03373c

@caspergasper
Copy link

Have you got this field set to not_analyzed in elasticsearch?

@nielsbasjes
Copy link
Author

I used a very basic logstash config to upload this data in to elasticsearch.
So I assume I have not set this.

@rashidkpc
Copy link
Contributor

Elasticsearch breaks fields into term, the pie chart uses a terms facet to get them back out. If you don't want a field broken into terms you need to set it as 'not_analyzed' using a template:

Here's a simple explanation:
https://github.com/logstash/logstash/wiki/Elasticsearch----Using-index-templates-&-dynamic-mappings

@wdaley
Copy link

wdaley commented Feb 19, 2014

I suggest this is a bug/necessary feature. If the itemization on the page can display the entire "user_agent" string, then the UI should support aggregating on it. Yes, I understand that elasticsearch does not work that way, but kibana, as the UI, should. Perhaps there should be an easy way to configure "not_analyzed" fields via kibana. The user-agent search is a really common use case and should not require a user to reconfigure elasticsearch by hand to support it.

@damonsmith
Copy link

The wiki appears to have disappeared, but I found that if I selected the type with the .raw extension in Kibana then I get the pie graph grouped correctly rather than splitting on spaces. I also don't know if that's a new thing or not but it worked for me.

harper-carroll pushed a commit to harper-carroll/kibana that referenced this issue Jul 11, 2016
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

Successfully merging a pull request may close this issue.

6 participants
@nielsbasjes @caspergasper @wdaley @rashidkpc @damonsmith and others