Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support for dynamically sending to multiple Graphite clusters #1

Open
naparuba opened this issue Aug 13, 2013 · 0 comments
Open

Support for dynamically sending to multiple Graphite clusters #1

naparuba opened this issue Aug 13, 2013 · 0 comments
Labels
enhancement

Comments

@naparuba
Copy link
Member

I think it would be useful to be able to send graphite data a system of choice. So Production / Staging/Dev can be separate graphite clusters to be be sent to.

Determining which to send to could be handled by a custom macro, much like the PRE/POST fix for metrics.
New modules could perhaps use something like tags to accept measurements

CF:shinken-solutions/shinken#933
@naparuba naparuba mentioned this issue Aug 13, 2013
Closed
Azef1 pushed a commit to Azef1/mod-graphite that referenced this issue Jul 12, 2016
Add options to enable\disable sending state
58756ab 
In graphite2.cfg, options are:
   state_enable 1 shinken-monitoring#1=enable send state / 0=disable
   state_host   1 shinken-monitoring#1=enable send state for host / 0=disable
   state_service 1 shinken-monitoring#1=enable send state for service / 0=disable
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@naparuba