Kibana: This interval creates too many buckets.

[beljul]

I'm currently working on a R script which is sending results into ElasticSearch through http requests. However when I try to simply plot my values according to my timestamps I get the following message :
This interval creates too many buckets to show in the selected time range, so it's has been scaled to 10 minutes.

During my analysis in R I already grouped my values by minute. That's why I would like to plot them into Kibana per minute and not per 10 minutes. Do you know why Kibana has this behavior ? (I'm using Kibana 4.0).

I have just one hour of data for now, so just 60 hits in ElasticSearch.

[shribigb]

You can force kibana to use custom interval.

In this example I have selected custom interval to be 30s. This will override kibana's selected auto interval.
Hope this helps

[beljul]

Thank you. However the problem is the same. Maybe it comes from the fact that I'm trying to plot data from two differents _type in the same time.

[beljul]

Okay it came from that, plot data splitting line based on the attribute _type. I now use an other attribute and it works well.

[devrimbaris]

I tested @shribigb 's answer without the second key in json (it gave an error in 2.4.7), and worked greatly.

[BastianVoigt]

Kibana 4.6.4 does not know "pre_zone_adjust_large_interval". It says:

Visualize: Unknown key for a VALUE_BOOLEAN in [2]: [pre_zone_adjust_large_interval].


Error: Request to Elasticsearch failed: {"error":{"root_cause":[{"type":"search_parse_exception","reason":"Unknown key for a VALUE_BOOLEAN in [2]: [pre_zone_adjust_large_interval].","line":1,"col":459}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"graylog_122","node":"9PuGYOSSRhaFeayie1PrTA","reason":{"type":"search_parse_exception","reason":"Unknown key for a VALUE_BOOLEAN in [2]: [pre_zone_adjust_large_interval].","line":1,"col":459}}]}}
    at http://kibana.test.infra.edeka.internal:5601/bundles/kibana.bundle.js?v=9732:79009:39
    at Function.Promise.try (http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:61111:23)
    at http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:61080:31
    at Array.map (native)
    at Function.Promise.map (http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:61079:31)
    at callResponseHandlers (http://kibana.test.infra.edeka.internal:5601/bundles/kibana.bundle.js?v=9732:78981:23)
    at http://kibana.test.infra.edeka.internal:5601/bundles/kibana.bundle.js?v=9732:78488:17
    at processQueue (http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:42357:29)
    at http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:42373:28
    at Scope.$eval (http://kibana.test.infra.edeka.internal:5601/bundles/commons.bundle.js?v=9732:43601:29)

[TIGERB]

@BastianVoigt same to your