Skip to content
This repository has been archived by the owner on Oct 12, 2019. It is now read-only.

Commit

Permalink
clarify usage of hostgroup_name for services
Browse files Browse the repository at this point in the history
  • Loading branch information
goetzk committed Mar 2, 2017
1 parent ca8dcb9 commit 3e2edd0
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,8 +53,11 @@ have not been implemented yet)
shinken_config_services: /etc/shinken/services/

# What services are we monitoring? which hostgroups do they apply to?
# NOTE: hostgroup_name missing means the test will be applied to ALL hostgroups.
# To apply to all except a subset of hosts use hostgroup_name: [ 'all!excludeme' ]
shinken_services:
- { service_description: 'ping test', command: 'check_ping', hostgroup_name: [] }
- { service_description: 'ping test', command: 'check_ping' }
- { service_description: 'port 80 test', command: 'check_tcp!80', hostgroup_name: ['webservers', 'proxies'] }

# Where should the host configuration go
shinken_config_hosts: /etc/shinken/hosts/
Expand Down Expand Up @@ -84,7 +87,7 @@ Including an example of how to use your role (for instance, with variables passe

- hosts: shinken
roles:
- { role: goetz.shinken, shinken_broker_modules: webui }
- { role: goetz.shinken, shinken_broker_modules: webui2 }

License
-------
Expand Down

0 comments on commit 3e2edd0

Please sign in to comment.