-
Notifications
You must be signed in to change notification settings - Fork 48
Redis backend? #32
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
Comments
I've been intending to move the reporters out of the gem to make the core gem have less dependencies. If you create a reporter gem for this, I would be happy to add a note in the readme and/or wiki. On Fri, Feb 22, 2013 at 8:23 AM, Alex Sharp [email protected]
|
Is there a convention for reporters already? Something like On Friday, February 22, 2013, Eric Lindvall wrote:
Cheers, alex sharp |
I have extracted the graphite one and just called it metriks-graphite, but in the case of redis I think it would be good to include reporter in the name to not conflict with someone writing metriks integration with a redis client. So, metriks-reporter-redis sounds good. On Fri, Feb 22, 2013 at 10:06 AM, Alex Sharp [email protected]
|
Are you interested in a redis reporter backend? I have one I'm working on, and I'd be happy to submit a PR if you're interested. Thanks for a great project ;)
The text was updated successfully, but these errors were encountered: