Bug #2634
nagios type serviceescalation should support servicegroup_name
| Status: | Closed | Start date: | 09/14/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  James Turnbull |
% Done: | 0% |
|
| Category: | nagios | |||
| Target version: | 0.25.1 | |||
| Affected Puppet version: | 0.24.8 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
Though not documented in http://nagios.sourceforge.net/docs/3_0/objectdefinitions.html#serviceescalation the serviceescalation definition in Nagios 3 supports using the parameter servicegroup_name as you can see in http://nagios.sourceforge.net/docs/3_0/objecttricks.html#serviceescalation (Under the header “All Services In Multiple Servicegroups:”).
Adding :servicegroup_name to the list of parameters in /usr/lib/ruby/site_ruby/1.8/puppet/external/nagios/base.rb (newtype :serviceescalation) did the trick for me.
History
Updated by James Turnbull over 2 years ago
- Category set to nagios
- Status changed from Unreviewed to Accepted
- Assignee set to James Turnbull
- Target version set to 0.25.1
Updated by James Turnbull over 2 years ago
- Status changed from Accepted to Closed
Pushed in commit:f2bc8aafcb9965b08a2442ed22b8942ade1f9b9d in branch 0.25.x