Dieterbe
commented
11 years ago hi. the suggested queries stuff is basically just a list of queries which i added to the template. queries which make sense for my environment at $dayjob but which I did not commit. I guess i could commit a few sample lines to demonstrate how it works. (I'll do that).
yes, the project is still young and will evolve. the pattern_graph stuff is deprecated (I mentioned this here and there in the docs) and I will rethink how that works.
yes ever increasing counters is something I want to add to the examples. (though I don't have a monitoring tool that actually generates them in graphite). But it should be trivial. You just create another target_type and override the generate_targets function. for default behavior just copy it from GraphTemplate but if id matches the name of your target_type set the target not just to match.string but to 'scaleToSeconds(nonNegativeDerivative(%s),1)' % match.string. that's all it takes.
rtoma
H[ea]llo Dieter,
On my quest to find a suitable dashboard for Graphite I found your project. Your project is much more intuitive than all those 'create & save graph' dashboards. I have been thinking about using RE to group metrics together, but your tagging solution makes it much more powerful and intuitive. Kudos!
While deepdiving in your code, I get the feeling that the project is not yet stabile. Is that correct? This feeling is based on the project homepage containing a screenshot with a 'suggested queries' listing, for which I could not find code. And I could not get the "pattern_graph" template config working (but maybe I need to look better).
An issue that's currently preventing me to do a real setup is the lack of support for rates (ever-increasing counters). Most of my metrics are not routed thru statsd and still require a scaleToSeconds(nonNegativeDerivative(my.metric),1) skeleton. Do you have a suggestion for me?
Keep on coding! And I will try to contribute.
Much appreciated / hartelijk bedankt,
Renzo