Hi Tobias, Just to make sure I'm understanding your suggestion:
The pre-processing step would aggregate data for the step size. It would compute any desired aggregate data, like averages and percentiles. The rrd table would then contain datasources for each of the aggregate values. I took a second look at the docs and tutorials and think I have a better understanding of how rrd works. I didn't realize initially that you give it the complete data for a step. I was under the impression that you could give it multiple values in the step and it would compute some of the aggregate values. Thanks again for the help. Regards, Liehann On Fri, Mar 27, 2009 at 11:55 AM, Tobias Oetiker <[email protected]> wrote: > Hi Liehann, > > if you don't mind the individual updates not going into the > database, then you can easily use rrdtool. you just may have to add > a pre-processing step that gobbles up the data from the webserver > for an rrd-step and then feeds it to rrdtool > > cheers > tobi > > >> Hi Tobias, >> >> My previous response should have been replied to the list, my >> apologies for the direct response. >> >> I also wanted to clarify - I wanted to roll up metrics into 1min, >> 5min, and 60min buckets, then graph metrics for the buckets over >> several hours / days. rrdtool already does pretty much everything - >> calculating averages, percentiles etc., which made it really >> appealing, but if, as you said, its not the right tool, then so be it. >> >> If anyone knows of a tool that can do these kind of metrics I would >> appreciate a link. So far everything Google returns seems to be backed >> by rrdtool, a sign that its a good tool I suppose :-) >> >> Regards, >> Liehann >> >> On Fri, Mar 27, 2009 at 8:42 AM, Tobias Oetiker <[email protected]> wrote: >> > Liehann, >> > >> > for per-call metrics, rrdtool is not the right choice. >> > >> > cheers >> > tobi >> > >> > >> > Today Liehann Loots wrote: >> > >> >> Hi, >> >> >> >> I'm investigation what the best tool would be for monitoring >> >> applications and web services. >> >> >> >> rrd seems pretty awesome but there is one problem I'm not sure how to >> >> work around. rrd stores data in second granularity. I want to store >> >> call metrics - for every call there will be a datapoint. If there is >> >> more than one call per second there will be more than one datapoint >> >> per second, which rrd can't store. >> >> >> >> Is there a way to solve this problem? >> >> >> >> Regards, >> >> Liehann >> >> >> >> _______________________________________________ >> >> rrd-users mailing list >> >> [email protected] >> >> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users >> >> >> >> >> > >> > -- >> > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland >> > http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 >> > >> >> _______________________________________________ >> rrd-users mailing list >> [email protected] >> https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users >> >> > > -- > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland > http://it.oetiker.ch [email protected] ++41 62 775 9902 / sb: -9900 > _______________________________________________ rrd-users mailing list [email protected] https://lists.oetiker.ch/cgi-bin/listinfo/rrd-users
