Send raw messages as "name:value|r|timestamp". This is compatible with https://github.com/jeffminard-ck/statsd/tree/raw_and_averages, currently pending a pull request into https://github.com/etsy/statsd. This format is also more consistent with other Etsy statsd message formats.

In wrapping the library for use in ChromiumOS's testing infrastructure, there were a couple small changes that are exceedingly hacky to maintain locally. Thus, here they are, I hope you find them agreeable. If you do, I'd much appreciate a pypi package bump afterwards.

This pull request cover two minor changes to make the library slightly easier to use:

• I have added methods to statsd.client.Client which give back an instance of whichever object type you have requested. I think this gives a cleaner interface than using the existing get_client() way.
• Made statsd.timer.Timer.start() return the timer instance so you can chain the instantiation and start of the timer, while still assigning the timer to a variable like this:
  timer = Timer('application_name').start()

I ask because I ran into issues while trying to install python-statsd through a proxy. e.g., ('pip install --proxy myproxy.net:80 python-statsd'). The install fails because its unable to download the setup_requires packages. If I remove the 'setup_requires', install succeeds.

Still trying to figure out the issue. Seems to be related with setuptools/ssl_support.py(184)https_open() though.

So the root cause of my install problem is not the setup_requires=['nose', 'mock', 'coverage'] line, but it made me wonder why this is even needed since these are test dependency modules. Are they needed for the package to function? If it's just for tests, should they be in tests_require?

I'm trying to measure the time of the invocations of small functions. The format for timers has my actual times as <1ms, so it's sending 0|ms. For my own use I'm sending %0.08f as the format for timers in that particular virtualenv so my problem isn't urgent, but I'd like to know if you've thought about this, e.g. passing in a format string for the timer so that the scale can be set by the caller?

In trying to manually use the following code:

timer = statsd.Timer(slug, connection=conn)
timer.send('total', seconds_taken)

...it would blow up with the exception AttributeError: 'Timer' object has no attribute 'logger'. This commit fixes that.

DEBUG: Bad line: 0,ms in msg "production.timer:0|ms" https://github.com/etsy/statsd/blob/5b900711191a9c5cfd536c877a3c119d1df5679a/lib/helpers.js Line 35: return isNumber(fields[0]) && Number(fields[0]) > 0;

statsD expects a > 0 number for ms counters.

Hello,

According to the pypi page at https://pypi.python.org/pypi/python-statsd this software is released under a BSD license. Would you be kind enough to add a copy of the license in the git source code as well as the copyright information? Thank you!

Hello,

Are you interested in supporting the multi-metric-packets functionality as described here: https://github.com/etsy/statsd/#multi-metric-packets

We are concerned with sending too many packets from our python applications.

I'd be happy to implement it and send a pull, just figured I'd ask if you don't support it for a reason.

I am not sure if this is a problem with how python-statsd is sending its data or how StatsD is processing and relaying to graphite, but there is some inconsistency that makes it hard to maintain a naming convention when sending metrics over.

For example, for counters, if we use a "my_counter" name, it displays like this on Graphite:

Graphite
`-- stats
    `-- my_counter

But for gauges or timers, they would add a prepending name depending on the name of the metric. So the above example will end up looking like this:

Graphite
`-- stats
    |-- timers
    |   |-- my_timer
    |-- gauges
    |   |-- my_gauge
    `-- my_counter

So timers and gauges prepend their name, but counters do not. If we try to use a naming convention (e.g. server name) it would be difficult to try and keep an order because of this.

I wasn't able to effectively find out what is missing here, but as far as I can tell python-statsd is sending the information correctly, without mangling the names we use.

Any ideas?

From https://github.com/etsy/statsd/blob/bf62f646d195f08fb17a37f7352be47366b2eaa9/stats.js#L120, any decimal/floating point number can be stored in a gauge by statsd. However, https://github.com/WoLpH/python-statsd/blob/master/statsd/gauge.py#L18 sends only an integer.

Example code:

from decimal import Decimal
import mock
import statsd

with mock.patch('statsd.Client') as mock_client:
    instance = mock_client.return_value
    instance._send.return_value = 1

    gauge = statsd.Gauge('testing')
    gauge.send('', 10.5)
    mock_client._send.assert_called_with(mock.ANY, {'testing': '10.5|g'}) # Actually sends '10|g'

    gauge.send('', Decimal('6.576'))
    mock_client._send.assert_called_with(mock.ANY, {'testing': '6.576|g'}) # Actually sends '6|g'

    gauge('', 1)
    mock_client._send.assert_called_with(mock.ANY, {'testing': '1|g'}) # Correctly sends '1|g'

pip install statsd python-statsd results in a mess in site-packages. Unlikely to be a real issue, only noticed because i was trying to figure out the differences between these and pystatsd, statsd-client