-
Notifications
You must be signed in to change notification settings - Fork 2
Gauge stats #13
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
base: master
Are you sure you want to change the base?
Gauge stats #13
Conversation
|
Where do you expect to use the gauge stats? |
|
I have a large system that today output statistics/metrics in different log files. Some of these are not counters but already averaged numbers such as avg events per second the last 30s. Sending these as counters to statsd did not provide accurate charts. Now, using gauges it's charting accurately. |
|
Also I created a gemspec file for the purpose of making it easier to distribute it to other hosts by orchestration software. I couldn't find any license on the rstatsd so I removed the default "MIT" license information. Would it be ok for you to set a license on it? |
New configuration parameter :interval. If :interval is set, stats are sent every :interval seconds, else if :every is set, stats are sent every :every row, else stats are sent once per second.
A really bad name for non-matching rows. Instead of throwing away non- matching rows, the unmetrics feature let's the user count those as well with the metrics names given by a list of "unmetrics".
If we use nested captures, we can get a MatchData set where some members are nil (meaning that that capture did not match anything). Those should not be counted
… to support Stefans new features
I implemented support for gauge stats. Also made the processctl compatible with ruby 1.9.x