Kibana Date histogram - interpretation

I am looking at the demo dashboard -

https://demo.elastic.co/app/kibana#/visualize/edit/37cc8650-b882-11e8-a6d9-e546fe2bba5f?_g=(refreshInterval:(pause:!f,value:900000),time:(from:'2020-03-25T11:15:07.466Z',to:'2020-04-12T18:30:00.000Z'))&_a=(filters:!(),linked:!f,query:(language:kuery,query:''),uiState:(),vis:(aggs:!((enabled:!t,id:'1',params:(field:total_quantity),schema:metric,type:sum),(enabled:!t,id:'2',params:(drop_partials:!f,extended_bounds:(),field:order_date,interval:w,min_doc_count:1,scaleMetricValues:!f,timeRange:(from:'2020-03-25T11:15:07.466Z',to:'2020-04-12T18:30:00.000Z'),useNormalizedEsInterval:!t),schema:segment,type:date_histogram),(enabled:!t,id:'3',params:(field:category.keyword,missingBucket:!f,missingBucketLabel:Missing,order:desc,orderBy:'1',otherBucket:!f,otherBucketLabel:Other,size:5),schema:group,type:terms)),params:(addLegend:!t,addTimeMarker:!f,addTooltip:!t,categoryAxes:!((id:CategoryAxis-1,labels:(show:!t,truncate:100),position:bottom,scale:(type:linear),show:!t,style:(),title:(),type:category)),dimensions:(series:!((accessor:1,aggType:terms,format:(id:terms,params:(id:string,missingBucketLabel:Missing,otherBucketLabel:Other)),params:())),x:(accessor:0,aggType:date_histogram,format:(id:date,params:(pattern:YYYY-MM-DD)),params:(bounds:(max:'2020-04-12T18:30:00.000Z',min:'2020-03-25T11:15:07.466Z'),date:!t,format:YYYY-MM-DD,interval:P7D,intervalESUnit:w,intervalESValue:1)),y:!((accessor:2,aggType:sum,format:(id:number),params:()))),grid:(categoryLines:!f,style:(color:%23eee)),labels:(),legendPosition:top,seriesParams:!((data:(id:'1',label:'Sum%20of%20total_quantity'),drawLinesBetweenPoints:!t,interpolate:linear,mode:stacked,show:true,showCircles:!t,type:area,valueAxis:ValueAxis-1)),thresholdLine:(color:%2334130C,show:!f,style:full,value:10,width:1),times:!(),type:area,valueAxes:!((id:ValueAxis-1,labels:(filter:!f,rotate:0,show:!t,truncate:100),name:LeftAxis-1,position:left,scale:(mode:normal,type:linear),show:!t,style:(),title:(text:'Sum%20of%20total_quantity'),type:value))),title:'',type:area))

Few questions
1 . I see a warning - This are may contain partial data. The selected time range does not fully cover it. What does it mean by partial data and how to interpret this message?

  1. Another question with respect to - how x axis metric were created like the following ( i see there is a gap of 4 days between each metric , when the histogram is created on the basis of orderdate per 12 hours . 2020-03-27 00:00 2020-03-31 00:00 2020-04-03 00:00 2020-04-07 00:00 2020-04-11 00:00

https://demo.elastic.co/app/kibana#/dashboard/722b74f0-b882-11e8-a6d9-e546fe2bba5f?_g=(refreshInterval:(pause:!f,value:900000),time:(from:'2020-03-25T11:15:07.466Z',to:'2020-04-12T18:30:00.000Z'))&_a=(description:'Analyze%20mock%20eCommerce%20orders%20and%20revenue',filters:!(),fullScreenMode:!f,options:(hidePanelTitles:!f,useMargins:!t),panels:!((embeddableConfig:(vis:(colors:('Men!'s%20Accessories':%2382B5D8,'Men!'s%20Clothing':%23F9BA8F,'Men!'s%20Shoes':%23F29191,'Women!'s%20Accessories':%23F4D598,'Women!'s%20Clothing':%2370DBED,'Women!'s%20Shoes':%23B7DBAB))),gridData:(h:10,i:'1',w:36,x:12,y:18),id:'37cc8650-b882-11e8-a6d9-e546fe2bba5f',panelIndex:'1',type:visualization,version:'7.5.1'),(embeddableConfig:(vis:(colors:(FEMALE:%236ED0E0,MALE:%23447EBC),legendOpen:!f)),gridData:(h:11,i:'2',w:12,x:12,y:7),id:ed8436b0-b88b-11e8-a6d9-e546fe2bba5f,panelIndex:'2',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:7,i:'3',w:18,x:0,y:0),id:'09ffee60-b88c-11e8-a6d9-e546fe2bba5f',panelIndex:'3',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:7,i:'4',w:30,x:18,y:0),id:'1c389590-b88d-11e8-a6d9-e546fe2bba5f',panelIndex:'4',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:11,i:'5',w:48,x:0,y:28),id:'45e07720-b890-11e8-a6d9-e546fe2bba5f',panelIndex:'5',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:10,i:'6',w:12,x:0,y:18),id:'10f1a240-b891-11e8-a6d9-e546fe2bba5f',panelIndex:'6',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:11,i:'7',w:12,x:0,y:7),id:b80e6540-b891-11e8-a6d9-e546fe2bba5f,panelIndex:'7',type:visualization,version:'7.5.1'),(embeddableConfig:(vis:(colors:('0%20-%2050':%23E24D42,'50%20-%2075':%23EAB839,'75%20-%20100':%237EB26D),defaultColors:('0%20-%2050':'rgb(165,0,38)','50%20-%2075':'rgb(255,255,190)','75%20-%20100':'rgb(0,104,55)'),legendOpen:!f)),gridData:(h:11,i:'8',w:12,x:24,y:7),id:'4b3ec120-b892-11e8-a6d9-e546fe2bba5f',panelIndex:'8',type:visualization,version:'7.5.1'),(embeddableConfig:(vis:(colors:('0%20-%202':%23E24D42,'2%20-%203':%23F2C96D,'3%20-%204':%239AC48A),defaultColors:('0%20-%202':'rgb(165,0,38)','2%20-%203':'rgb(255,255,190)','3%20-%204':'rgb(0,104,55)'),legendOpen:!f)),gridData:(h:11,i:'9',w:12,x:36,y:7),id:'9ca7aa90-b892-11e8-a6d9-e546fe2bba5f',panelIndex:'9',type:visualization,version:'7.5.1'),(embeddableConfig:(),gridData:(h:18,i:'10',w:48,x:0,y:54),id:'3ba638e0-b894-11e8-a6d9-e546fe2bba5f',panelIndex:'10',type:search,version:'7.5.1'),(embeddableConfig:(isLayerTOCOpen:!f,mapCenter:(lat:45.88578,lon:-15.07605,zoom:2.11),openTOCDetails:!()),gridData:(h:15,i:'11',w:24,x:0,y:39),id:'2c9c1f60-1909-11e9-919b-ffe5949a18d2',panelIndex:'11',type:map,version:'7.5.1'),(embeddableConfig:(),gridData:(h:15,i:'12',w:24,x:24,y:39),id:b72dd430-bb4d-11e8-9c84-77068524bcab,panelIndex:'12',type:visualization,version:'7.5.1')),query:(language:kuery,query:''),timeRestore:!t,title:'%5BeCommerce%5D%20Revenue%20Dashboard',viewMode:view)

The chart is using weekly aggregations. Each bucket starts on Monday, but the selected range starts on Wednesday March 25th. The warning says that the first bucket contains partial data because only contains the data from the week starting on March 23, but starting from wednesday.

Seems that the link provided is a link to a dashboard. I'm not sure what chart you are referring to in this case

The chart is using weekly aggregations. Each bucket starts on Monday, but the selected range starts on Wednesday March 25th. The warning says that the first bucket contains partial data because only contains the data from the week starting on March 23, but starting from Wednesday.

Monday seems to be default for weekly aggregations . Why it cant be use the week as starting day for the aggregation , so ,Wednesday in this case. But , then the last bucket might not have complete range. Sounds fine !!

Seems that the link provided is a link to a dashboard. I'm not sure what chart you are referring to in this case.

Please refer widget - [eCommerce] Sales by Category - X axis

Yes, Monday is the default, but can be configured on the Advanced Settings dateFormat:dow.

The X axis in case is just showing a limited number of ticks, not all the existing one. If you move your mouse over the chart areas you will see that there are data points on every 12 hours. Rendering all the ticks every 12 hours means to overlap the text labels each other, so the chart renderer just hide some of them to avoid this overlap.
If you increase the size of your browser or of the visualization you can see all the available ticks

Got it, so it was decided with a guess to hide some labels to prevent them from overlapping each other .Is there any setting i can update to see all the labels ?

Not that I'm aware of at the moment, unfortunately.
This charting library is rather old and we are going to move toward our own chart library.
This will allow increasing the number of ticks displayed on the chart, displaying all the labels overlapping labels and so. But this change will be available in some future version of Kibana
In the meantime you can play with the axis options available on the chart, changing the alignment of the ticks to be angled or vertical, but I'm pretty sure this will not fix the issue.

Great. Thanks. I got all the inputs I needed at this moment

Hi Marco, I'm attempting to change a date histogram's weekly aggregation on my cloud.elastic.co install, and the dateFormat:dow value isn't having any effect. I notice that there is an open case on this topic at https://github.com/elastic/kibana/issues/24960 that suggests using offset to fix this. This is OK as a workaround, but it seems you are suggesting this workaround shouldn't be needed?

Also my issue with this dow setting is wider than just aggregations, as it extends also to the setting not being respected for week alignment datemath using "/w". I notice that this issue was raised and closed as "not reproducible" at https://github.com/elastic/kibana/issues/14495, but I am definitely seeing this issue right now!

I'm in AEST timezone and using ElasticSearch/Kibana 7.5 if it makes a difference...

Thanks! Jason

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.