# Moving Average aggregation does not work with data points
**URL:** https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226
**Category:** Kibana
**Created:** [June 29, 2016, 4:24am UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226 "2016-06-29T04:24:17Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)
#### Post date: [June 29, 2016, 4:24am UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/1 "2016-06-29T04:24:17Z")
Hi everyone,
I am using Elasticsearch 2.3.2, and Kibana 4.5.0 with Timelion plugin to generate visualization data at the moment. Nevertheless, there is an issue in regard of Timelion. The issue comes with the **MOVINGAVERAGE** function. I have made a queries in order to generate timeseries chart of a year.
`.es(index='linux_cpu-*', metric='avg:CPU(%)').movingaverage(10)`
It seems there is nothing wrong with this query but it could not give out a desired result. It gives out a graph as shown below which the metric will becomes 0 at the end point.
What is the problem?
---
### Author:  [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)
#### Post date: [June 29, 2016, 6:16pm UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/2 "2016-06-29T18:16:04Z")
Does your data cut off around 2015-02-01? Perhaps it's using 0 for the values instead of not using any value?
---
### Author:  [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)
#### Post date: [June 29, 2016, 11:47pm UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/3 "2016-06-29T23:47:40Z")
Yes Thr data point cutoff at 2015-02-01
But I didnt input any datapoint contains 0 value
How should I make a correct graph
---
### Author:  [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)
#### Post date: [June 30, 2016, 4:55pm UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/4 "2016-06-30T16:55:13Z")
It's possible that the visualization library is casting null values as 0, and so you end up with what you see now. It may be intentional, it may be a bug, or perhaps the query needs to be tweaked. Unfortunately I'm not well versed in Timelion myself.
@Rashid\_Khan can you provide any insight?
---
### Author:  [@Kennedy\_Kan1](https://discuss.elastic.co/u/Kennedy_Kan1)
#### Post date: [July 3, 2016, 4:46am UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/5 "2016-07-03T04:46:29Z")
Maybe is there any function based on kibana that can generates temporary future value and use that as a basis to do moving average?
---
### Author:  [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)
#### Post date: [July 5, 2016, 4:43pm UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/6 "2016-07-05T16:43:41Z")
There's wouldn't be anything Kibana can do, Timeline is a standalone app with its own visualizations and rendering.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:48pm UTC](https://discuss.elastic.co/t/moving-average-aggregation-does-not-work-with-data-points/54226/7 "2017-07-06T13:48:15Z")