cookbook 'opsmatic', '= 0.1.24'
opsmatic (3) Versions 0.1.24 Follow0
Installs/Configures Opsmatic services and integrations
cookbook 'opsmatic', '= 0.1.24', :supermarket
knife supermarket install opsmatic
knife supermarket download opsmatic
opsmatic Cookbook
This cookbook contains various recipes to help you with integrating your infrastructure with Opsmatic. The recipes
contained in this cookbook are as follows:
opsmatic::handler
This recipe configures a report and exception handler that sends detail on successful and failed runs to Opsmatic
opsmatic::agent
This recipe configures the opsmatic collection agent
opsmatic::file-integrity-monitoring
This recipe configures file monitoring for the agent
Requirements
opsmatic::handler
The Opsmatic report handler depends on the chef_handler cookbook
Attributes
-
node[:opsmatic][:integration_token]
- You must configure this attribute with your integration token. You can find your integration token on the Integrations page in your Opsmatic account.
opsmatic::handler
-
node[:opsmatic][:ssl_peer_verify]
- Enables/Disable OpenSSL peer verification. Defaults to false (no peer verificaiton) until we can work out a consistent and reliable way to make this work for everyone. -
node[:opsmatic][:handler_version]
- Version of the chef-handler-opsmatic rubygem to use. We suggest you set this attribute somewhere globally in your environment, we'll notify you when upgrades are available and you can bump the version number.
opsmatic::agent
-
node[:opsmatic][:agent_action]
- determines whether chef should attept toupgrade
the agent on every subsequent run -
node[:opsmatic][:handler_version]
- pins the agent to a specific version. Default behavior is to install the latest available version the first time around and stay put after that. -
node[:opsmatic][:host_alias]
- specifies the host's alias in/etc/opsmatic-agent.conf
-
node[:opsmatic][:groups]
- specifies the group that a host belongs to in/etc/opsmatic-agent.conf
More information regarding the latter two attributes can be located here
opsmatic::file-integrity-monitoring
-
node[:opsmatic][:file-monitor-list]
- takes an array of strings that contain file paths for file integrity monitoring:"file-monitor-list": ['/etc/nginx/nginx.conf','/etc/ssh/sshd_config','/etc/rsyslog.conf','/etc/hosts','/etc/passwd']
Usage
opsmatic::handler && opsmatic::agent
To wire the handler into your infrastructure, add the opsmatic::handler
recipe as the first item in the run list
of your node or role (You will need to use the agent as well).
{ "name": "my_node", "run_list": [ "recipe[opsmatic::handler]", "recipe[opsmatic::agent]" ] }
The attributes will look something like this:
"attributes": { "opsmatic": { "integration_token": "YOUR-INTEGRATION-TOKEN", "file-monitor-list": ["/etc/nginx/nginx.conf","/etc/ssh/sshd_config","/etc/rsyslog.conf","/etc/hosts","/etc/passwd"], "host_alias": "chefcookbookhostname", "groups": ["groupone", "anothergroup", "yetanothergroup"] } }
To install just the agent remove the opsmatic::handler recipe.
Contributing
- Fork it ( https://github.com/opsmatic/opsmatic-cookbook/fork )
- Create your feature branch (
git checkout -b my-new-feature
) - Commit your changes (
git commit -am 'Add some feature'
) - Push to the branch (
git push origin my-new-feature
) - Create a new Pull Request
Dependent cookbooks
chef_handler <= 1.1.8 |
apt >= 0.0.0 |
Contingent cookbooks
There are no cookbooks that are contingent upon this one.
Changelog
0.1.0 / 2014-06-05
- initial release
0.1.1 / 2014-06-06
- allow enable/disable of SSL peer verification via attribute
Foodcritic Metric
0.1.24 failed this metric
FC031: Cookbook without metadata file: /tmp/cook/7b09213952517f98b13bf71c/opsmatic/metadata.rb:1
FC045: Consider setting cookbook name in metadata: /tmp/cook/7b09213952517f98b13bf71c/opsmatic/metadata.rb:1
0.1.24 failed this metric
FC045: Consider setting cookbook name in metadata: /tmp/cook/7b09213952517f98b13bf71c/opsmatic/metadata.rb:1