-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kudos and how to deal with rates? #4
Comments
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 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 |
hey, i pushed the suggested queries feature: 66eb072 |
thanks! |
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
The text was updated successfully, but these errors were encountered: