Graphite

retention and graphing

Asked by Carolyn Bray

We are testing with retention and the storage-aggregation.conf and found what might be a bug.

We put in a retention time of (archive=[(1, 3600), (60, 20160)

I then entered some fake data - we were also trying to exercise storage-aggregation.conf, but the strange part is that when the data below is put into graphite, I see different values for the "200" value. If I look at a long time frame around the data, it reads 50. If I close in more, it is 100. If I go even tighter - to just cover the time of the datapoints below, it reads the full 200.

If it simply the graph can't display the resolution? I tried increasing the size of the graph on my screen and it was still displaying as though the data were 50.

In addition, the data did drop and retain with an average - but even then the graph was acting strangly as I view the time when the retention would change.

Anyone have any bright ideas?

2 1361218010
2 1361218011
2 1361218012
2 1361218013
2 1361218014
2 1361218015
2 1361218016
2 1361218017
2 1361218018
2 1361218019
200 1361218020
2 1361218021
2 1361218022
2 1361218023
2 1361218024
2 1361218025
2 1361218026
2 1361218027
2 1361218028
2 1361218029
2 1361218030
2 1361218031
2 1361218032
2 1361218033
2 1361218034
2 1361218035
2 1361218036
2 1361218037
2 1361218038
2 1361218039
2 1361218040
2 1361218041
2 1361218042
2 1361218043
2 1361218044
2 1361218045
2 1361218046
2 1361218047
2 1361218048
2 1361218049
2 1361218050
2 1361218051
2 1361218052
2 1361218053
2 1361218054
2 1361218055
2 1361218056
2 1361218057
2 1361218058
2 1361218059
2 1361218060
2 1361218061
2 1361218062
2 1361218063
2 1361218064
2 1361218065
2 1361218066
2 1361218067
2 1361218068
200 1361218069
2 1361218070
2 1361218071
2 1361218072
2 1361218073
2 1361218074
2 1361218075
2 1361218076
2 1361218077
2 1361218078
2 1361218079
200 1361218080
2 1361218081
2 1361218082
2 1361218083
2 1361218084
2 1361218085
2 1361218086
2 1361218087
2 1361218088
2 1361218089
2 1361218090
2 1361218091
2 1361218092
2 1361218093
2 1361218094
2 1361218095
2 1361218096
2 1361218097
2 1361218098
2 1361218099
2 1361218100
2 1361218101
2 1361218102
2 1361218103
2 1361218104
2 1361218105
2 1361218106
2 1361218107
2 1361218108
2 1361218109
2 1361218110
2 1361218111
2 1361218112
2 1361218113
2 1361218114
2 1361218115
2 1361218116

Question information

Language:
English Edit question
Status:
Answered
For:
Graphite Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Nicholas Leskiw (nleskiw) said : 		#1

If you have more than one datapoint per pixel, graphite will average all
datapoints and draw the average.

You may want to try the consolidateBy(foo.bar.baz,"max") function if you do
not like this behavior.

-Nick

On Mon, Feb 18, 2013 at 3:06 PM, Carolyn Bray <
<email address hidden>> wrote:

> New question #222220 on Graphite:
> https://answers.launchpad.net/graphite/+question/222220
>
> We are testing with retention and the storage-aggregation.conf and found
> what might be a bug.
>
> We put in a retention time of (archive=[(1, 3600), (60, 20160)
>
> I then entered some fake data - we were also trying to exercise
> storage-aggregation.conf, but the strange part is that when the data below
> is put into graphite, I see different values for the "200" value. If I
> look at a long time frame around the data, it reads 50. If I close in
> more, it is 100. If I go even tighter - to just cover the time of the
> datapoints below, it reads the full 200.
>
> If it simply the graph can't display the resolution? I tried increasing
> the size of the graph on my screen and it was still displaying as though
> the data were 50.
>
> In addition, the data did drop and retain with an average - but even then
> the graph was acting strangly as I view the time when the retention would
> change.
>
> Anyone have any bright ideas?
>
> 2 1361218010
> 2 1361218011
> 2 1361218012
> 2 1361218013
> 2 1361218014
> 2 1361218015
> 2 1361218016
> 2 1361218017
> 2 1361218018
> 2 1361218019
> 200 1361218020
> 2 1361218021
> 2 1361218022
> 2 1361218023
> 2 1361218024
> 2 1361218025
> 2 1361218026
> 2 1361218027
> 2 1361218028
> 2 1361218029
> 2 1361218030
> 2 1361218031
> 2 1361218032
> 2 1361218033
> 2 1361218034
> 2 1361218035
> 2 1361218036
> 2 1361218037
> 2 1361218038
> 2 1361218039
> 2 1361218040
> 2 1361218041
> 2 1361218042
> 2 1361218043
> 2 1361218044
> 2 1361218045
> 2 1361218046
> 2 1361218047
> 2 1361218048
> 2 1361218049
> 2 1361218050
> 2 1361218051
> 2 1361218052
> 2 1361218053
> 2 1361218054
> 2 1361218055
> 2 1361218056
> 2 1361218057
> 2 1361218058
> 2 1361218059
> 2 1361218060
> 2 1361218061
> 2 1361218062
> 2 1361218063
> 2 1361218064
> 2 1361218065
> 2 1361218066
> 2 1361218067
> 2 1361218068
> 200 1361218069
> 2 1361218070
> 2 1361218071
> 2 1361218072
> 2 1361218073
> 2 1361218074
> 2 1361218075
> 2 1361218076
> 2 1361218077
> 2 1361218078
> 2 1361218079
> 200 1361218080
> 2 1361218081
> 2 1361218082
> 2 1361218083
> 2 1361218084
> 2 1361218085
> 2 1361218086
> 2 1361218087
> 2 1361218088
> 2 1361218089
> 2 1361218090
> 2 1361218091
> 2 1361218092
> 2 1361218093
> 2 1361218094
> 2 1361218095
> 2 1361218096
> 2 1361218097
> 2 1361218098
> 2 1361218099
> 2 1361218100
> 2 1361218101
> 2 1361218102
> 2 1361218103
> 2 1361218104
> 2 1361218105
> 2 1361218106
> 2 1361218107
> 2 1361218108
> 2 1361218109
> 2 1361218110
> 2 1361218111
> 2 1361218112
> 2 1361218113
> 2 1361218114
> 2 1361218115
> 2 1361218116
>
> --
> You received this question notification because you are a member of
> graphite-dev, which is an answer contact for Graphite.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~graphite-dev
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~graphite-dev
> More help : https://help.launchpad.net/ListHelp
>

Can you help with this problem?

Provide an answer of your own, or ask Carolyn Bray for more information if necessary.

To post a message you must log in.