search for: nagios_service

It seems that the nagios_service type will not write out the "name" property of nagios service objects. I had thought this was an oversight or a bug, till I saw this thread: http://www.mail-archive.com/puppet-bugs@googlegroups.com/msg10387.html which seems to imply that this is a deliberate "feature". Is th...

...ted resources This was inspired by my reading all of the nagios related recipes that went something along the lines of class nagios { package {nagios: ensure=> latest } service {nagios : ensure => running , enable => true} Nagios_host <<! !>> Nagios_service <<! |> class target { @@nagios_host { $fqdn: ensure => present, alias => $hostname, register => 1,...

...sted in details, see: http://wp.me/p1RukY-1n. Thanks for helping, Gabriel! Bernd > -----Ursprüngliche Nachricht----- > Von: Bernd Adamowicz [mailto:info@bernd-adamowicz.de] > Gesendet: Donnerstag, 17. November 2011 22:36 > An: Bernd Adamowicz > Betreff: Fwd: Re: [Puppet Users] AW: nagios_service does not replace > target file > > > > ------- Forwarded message ------- > From: "Bernd Adamowicz" <info@bernd-adamowicz.de> > To: puppet-users@googlegroups.com > Cc: > Subject: Re: [Puppet Users] AW: nagios_service does not replace target > file &gt...

...I''m using a lot of nagios_ commands in my puppet manifests and I saw a problem when using ''undef'' in exported resources : Here is a simple example : define nagios::service::distributed ($ensure=present, $service_description, $host_name=false, $contact_groups=false) { nagios_service {$name: ensure => $ensure, use => "generic-service-active", host_name => $host_name ? {false => $hostname, default => $host_name}, check_command => $name, tag => "nagios", service_description => $service_description, target =&g...

...able to solve. When the stored configs are purged from puppet the nagios server correctly removes them from the services and hosts file but does not notify the nagios service and instead throws an error. So the entries are still there and nagios still reports on them until it is restarted. (/Nagios_service[check_ping_jasontest2.wishabi.net]) Whit[Completed_stage[main]],Whit[Completed_class[Nagios3_monitor]],Service[nagios3] still depend on me -- not purging The reason that I want this feature is that I have created several automation scripts so I can start a service through AWS giving it two tags...

...re of the way that there is no concept of unmanaging something and when this is in the context of a file ownership or whatever, then that makes sense. But when this is applied to things like nagios configuration data the principle seems to come unstuck. Or at least, it seems so to me. Say I have a nagios_service which uses another template nagios_service. I am about to rejig my existing configuration to permit some mechanism to override the default settings, e.g. override the command value from the default in the template service to some host specific setting, something (probably syntactially wrong) like.....

...nately this means the monitoring server takes about 8 minutes to perform a Puppet run. I''m not exactly sure what the bottleneck is - whether it''s doing 3000 calls to PuppetDB (although the load on the PuppetDB server and its Postgres database are low), or whether it is parsing nagios_service.cfg that causes the slowdown. It''s about 500kb and 11,000 lines. I know it is possible to squirt the Nagios config into several smaller files when the resources are collected on the monitoring server, but I gather this also means that Nagios resources cannot be purged if the default f...

...e { nagios3: ensure => running, alias => nagios, hasstatus => true, hasrestart => true, require => Package[nagios], } # collect resources and populate /etc/nagios/nagios_*.cfg Nagios_host <<||>> Nagios_service <<||>> Nagios_hostextinfo <<||>> class target { @@nagios_host { $fqdn: ensure => present, alias => $hostname, address => $ipaddress, use => "generic-host", } @@nagios_hostextinfo { $fqdn:...

Hi all, I''m working on setting up Puppet to write out my Nagios configs. A few weeks back I inserted a few dummy Nagios checks into my Puppet config, and the Nagios configs were written out properly. I''ve now added loads of Nagios host and service checks like this: @@nagios_service { "check_smtp_${hostname}": check_command => "check_nrpe!check_smtp", host_name => "$fqdn", service_description => "SMTP", } and then I collect them like this: Nagios_host <<||>> Nagios_service <<||>> Nagios_host...

Hi, I have a Ruby class in "nagios" module - it''s located in nagios/ manifests/ssa_nagios_checks.rb and looks like this hostclass :ssa_nagios_checks do ... end In nagios/manifests/init.pp I have class nagios::server { ... include ssa_nagios_checks ... } And I get the following error .... debug: importing ''/etc/puppet/modules/nagios/manifests/

...s.puppetlabs.com/guides/exported_resources.html, and I''m doing that now. However, it has some problems: - puppet runs are very slow on the nagios node - when I want to change the service configuration in nagios, I have to wait for all my puppet agents to check in so they can export a new nagios_service, then wait for the nagios node to check in to pick up the exported service - the nagios configuration is hard to read with human eyes because the same service definition is repeated many times, once per node I''d much rather configure nagios like most people would do it if they weren'...

.... Now let''s look at how Puppet "wants" to configure Nagios: Each host exports a unique service for each of the checks it should be subject to. Holy cow! So if I have 25 checks per machine, and a thousand nodes, that''s 25,000 entries! We''re talking about a nagios_services.cfg measured in the tens of *megabytes*! I''m a little stunned by this pattern. I had created a system whereby nodes exported concat::fragments expressing desired membership in a hostgroup, and defines that created services, hostgroups, and servicegroups only if they hadn''t alre...

hello, i wondered if it would not be interesting to have some filters function in puppet like filter_integer(), filter_prelregex, filter_text, filter_email or such so we can validate and make our defines a little more foolproof :) i particulary see filter_regex as usefull in quite a lot of exec that manipulates text files. What do you think about this ? -- Cordialement, Ghislain