Closed RCheesley closed 10 months ago
Was there any thought on how to resolve this?
Hi @RCheesley,
I'm sorry, I didn't see this issue. I found a workaround for that, it is not perfect though.
Here is the workaround I found some time ago:
Date Histogram
and select the field you want.Interval
to Custom
and 4M
(yes, longer than a quarter, this avoids possible overlappings because Kibana is going to draw the chart based on this, but translating it to days and elasticsearch is responding with real quarters, so we need Kibana to draw longer intervals to make sure bars are not going to overlap).
Open Advanced
section at the bottom and set the JSON input
text field to: {"interval": "quarter"}
.(*) Interval field seems to be used by Kibana to set charts width, but not passed in the underlying ES query for data (see interval within the request JSON body):
Hope it helps!
Alberto.
Thanks for the suggestion, I'll look into that for sure!
Hi there,
This partially addresses the issue however it concerns me that this seems to suggest there is data coming in from July when it shouldn't be:
At this point, I fear this is a Kibana issue and I'm not sure whether we could find a workaround for this in the vertical bar chart visualization. Maybe timelion or Vega visualizations could provide other ways to deal with this.
Hi folks,
Trying to group a date histogram by quarter but struggling - see screencap:
https://www.youtube.com/watch?v=fmIbaawSFqg
Any suggestions?