On Thursday, March 20, 2014 2:30:55 PM UTC+1, Xwilly Azel wrote: > I have the same issue with your version and I don't see where in kibana i can > say : disable zero-fill checkbox. > > On Thursday, March 20, 2014 2:29:24 PM UTC+1, Xwilly Azel wrote:On Thursday, > March 20, 2014 1:15:44 PM UTC+1, Isaac Hazan wrote: > > > The attached as well. > > > It’s another way to circumvent the problem > > > > > > From: [email protected] [mailto:[email protected]] On > > Behalf Of Xwilly Azel > > > Sent: Thursday, March 20, 2014 1:06 PM > > > To: [email protected] > > > Subject: Re: Kibana Histogram unexpected line curve with cumulative value > > > > > > > > > here my inspect from kibana : > > > > > > > > > > > > > > > > > > > > > curl -XGET > > 'http://xxxxx:9200/logstash-2014.03.20,logstash-2014.03.19/_search?pretty' > > -d '{ > > > > > > "facets": { > > > > > > "0": { > > > > > > "date_histogram": { > > > > > > "key_field": "@timestamp", > > > > > > "value_field": "gclog.gc.mem.after", > > > > > > "interval": "1h" > > > > > > }, > > > > > > "global": true, > > > > > > "facet_filter": { > > > > > > "fquery": { > > > > > > "query": { > > > > > > "filtered": { > > > > > > "query": { > > > > > > "query_string": { > > > > > > "query": "gc.type:GC OR gc.type:Full" > > > > > > } > > > > > > }, > > > > > > "filter": { > > > > > > "bool": { > > > > > > "must": [ > > > > > > { > > > > > > "range": { > > > > > > "@timestamp": { > > > > > > "from": 1395227019780, > > > > > > "to": "now" > > > > > > } > > > > > > } > > > > > > } > > > > > > ] > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > } > > > > > > }, > > > > > > "size": 0 > > > > > > }' > > > > > > > > > On Thursday, March 20, 2014 12:00:29 PM UTC+1, Xwilly Azel wrote: > > > > > > I've upgrader to kibana 3.0.0. > > > > > > > > > > > > Still the same issue, when I 'm doing an histogram, I don't have option to > > disable zero-fill checkbox. > > > > > > > > > > > > > > > On Thursday, March 20, 2014 8:22:35 AM UTC+1, Isaac Hazan wrote: > > > > > > > > > Yes, the problem is because when the histogram encounters buckets with no > > data it assumes zero values instead of joining the points between the 2 > > interval. > > > I solved it by using a different kibana version, I effectively found 2 > > patches one with a zero-fill checkbox and another one with an option box. I > > found just one of them: > > > https://github.com/elasticsearch/kibana/issues/741 > > > > > > Both versions solve the problem. > > > > > > That’s the way I solved it. > > > > > > Hope that helps > > > > > > /Itzhak > > > > > > From: [email protected] [mailto:[email protected]] On > > Behalf Of Xwilly Azel > > > Sent: Thursday, March 20, 2014 9:12 AM > > > To: [email protected] > > > Subject: Re: Kibana Histogram unexpected line curve with cumulative value > > > > > > > > > I've got the same kind of issue. > > > > > > > > > > > > Did you find a solution ? > > > > > > On Monday, March 10, 2014 3:58:21 PM UTC+1, Isaac Hazan wrote: > > > > > > Kibana cannot do a the Histogram of the cumulative value of a field as > > describe at:https://github.com/elasticsearch/kibana/issues/740 > > > To overcome that I created a separate index where I calculate myself the > > total and saved it to Elasticsearch. > > > The mapping looks as follows:curl -XPOST localhost:9200/first_install -d '{ > > "settings" : { "number_of_shards" : 5 }, "mappings" : { > > "fi" : { "properties" : { "evtTime" : { "type" > > : "date", "index": "not_analyzed", "format": "dd/MMM/yyyy:HH:mm:ss" }, > > "cumulativeValue" : { "type" : "integer", "index": "not_analyzed" > > } } } }}' > > > The values are saved properly but unexpectedly Kibana does not draw the > > line i would expect, instead it joins between point that do not exist. > > > Following is the Kibana sreenshot: > > > The line curve should always be increasing since my data set is always > > increasing, that i can prove by the following events as seen by kibana > > itself: > > > Could it be related to the data formatting I did? > > > Thx in advance. > > > -- > > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/elasticsearch/mp2hUkR8U6w/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/elasticsearch/9fe1f350-c5fb-47f2-8925-2d52b7376d94%40googlegroups.com. > > > For more options, visit https://groups.google.com/d/optout. > > > -- > > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/elasticsearch/mp2hUkR8U6w/unsubscribe. > > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/elasticsearch/71e13a70-e6a6-4896-a050-62f2462ab085%40googlegroups.com. > > > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/1e5aa19c-0132-4432-80c6-6542dd789bcb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
<<attachment: image.jpg>>
