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

Allow additional (non-chef) nodes to be specified. #52

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

julianrutten
Copy link

The README and commit messages are pretty explanatory, if you have any questions let me know.

…) by setting the munin.nodes variable. This is an array of objects, which take the same fqdn and ipaddress keys as the node search returns by default. Also this enables to reach servers hidden behind a firewall through munin native ssh.
@shortdudey123
Copy link

FWIW node['munin']['server_list'] already does this

@whatcould
Copy link

This is very useful! Would be great to get this in the main fork.

Note that, contrary to the comment above, this does not do the same thing as `node['munin']['server_list'] — that option is for munin-client and specifies what servers are allowed to connect.

This pull request allows you to tell a munin-server to fetch information from other nodes besides those existing in your chef recipe. For example, I have one server I use as a munin server for all my other servers/clusters, rather than setting up a munin server for each separate app; for that server I have to give it a list of nodes.

It's probably clear from the Readme, but here's how nodes are specified:

"nodes": [
      {"fqdn": "myapp-name", "ipaddress": "10.0.0.1"},
      {"fqdn": "anotherapp-name", "ipaddress": "10.0.0.2"},
]

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

Successfully merging this pull request may close these issues.

3 participants