Skip to content

Conversation

@Ulrhol
Copy link

@Ulrhol Ulrhol commented Sep 27, 2014

I implemented support for gauge stats. Also made the processctl compatible with ruby 1.9.x

@wwarner-ideeli
Copy link

Where do you expect to use the gauge stats?

@Ulrhol
Copy link
Author

Ulrhol commented Sep 27, 2014

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.

@Ulrhol
Copy link
Author

Ulrhol commented Sep 27, 2014

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?

Ulrhol and others added 13 commits September 27, 2014 21:30
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants