Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Connecting graphite with an SSL certificate. #333

wants to merge 7 commits into


None yet
4 participants

athoune commented Aug 28, 2013

I want to use statsd in an half private context. Statsd daemon only listen in localhost, with an arbitrary key prefix and push data to a mutualised carbon. I don't want to use AMQP protocol for using authentication, so I just put a Stunnel on the Carbon server. I can put a Stunnel client side too, but nodejs play nice with SSL. Here is the patch to handle SSL connection with client certificate to carbon, for statsd.

Here is the original blog post:


mrtazz commented Sep 1, 2013

Thanks for the pull request, the changes look good. Can you add the new configuration bits also in exampleConfig.js and move them under the graphite key? I know it's not really consistent right now, but eventually I want all graphite configuration to live under that key to make it clearer.

athoune commented Sep 4, 2013

I synchronized with your branch (with few conflicts), then fixing what you suggest.

athoune commented Nov 7, 2013

Did I forget something?

Any chance this might be revisited at some point? Certainly value here, there's more and more third party graphite providers where I'd prefer to send the stats securely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment