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.

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

Handle split redis/api/rabbit hosts, hosted redis. #25

Open
jhmartin opened this issue Aug 13, 2014 · 2 comments
Open

Handle split redis/api/rabbit hosts, hosted redis. #25

jhmartin opened this issue Aug 13, 2014 · 2 comments

Comments

@jhmartin
Copy link
Contributor

The rabbit/redis/api servers may be on different hosts (and perhaps not even search()able in the case of AWS hosted redis). It would be useful if the search blocks could be separated and also overrideable by a static value.

@rodriguezsergio
Copy link

Use node.force_override in a wrapper cookbook to get around this issue. That's what I'm doing for my rabbitMQ cluster and it works fine. The force_override precedence is higher than override, so node.override["sensu"]["redis"]["host"] = master_address doesn't supersede your custom value.

@portertech
Copy link
Owner

This cookbook is an example wrapper cookbook for Sensu, most users must fork it in order to use it. I'm open to a pull-request that improves the user experience for this deployment method/configuration.

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

No branches or pull requests

3 participants