Displaying 11 results from an estimated 11 matches for "nagios_hosts".
Did you mean:
nagios_host
2008 Nov 14
0
Why no hostgroups parameter for nagios_host types?
...And before anyone asks why I can''t use the
nagios_hostgroup type, if someone can tell me how I can collect
members without having to manage the hostgroup members manually, that
would be fantastic.
There''s a servicegroups parameter for services, how has hostgroups
been left out of nagios_hosts for so long?
Scott
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to puppet...
2012 Jan 17
4
Exported variable foo...(fu?)
Hi folks,
For the first time since I started playing with puppet I started down the
road of using exported 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 <<! !>>
2013 Jan 21
15
Terrible exported resources performance
Hi,
Since the below is a little long, I put my question at the top: how do I
troubleshoot awful exported resources performance in puppet and is there
anything I can tweak to get it to run under 10 minutes in larger
environments?
I have a fairly modest environment (118 nodes, but prod will be at least
twice as large). I''m trying to move my distributed nagios setup to one
based on
2008 Jun 13
12
puppet/naginator?
I''m very interested in the way that puppet appears to be able to
generate nagios configurations though I can''t seem to find any
documenation on how it works:
http://reductivelabs.com/trac/naginator
is clearly a placeholder page...
Meanwhile the various pieces of info at links such as:
http://reductivelabs.com/trac/puppet/wiki/TypeReference#nagios-host
are just teasing me.
2012 Sep 10
5
Nagios purge deleted items and notify nagios service problem
I am using stored configs to manage my nagios host and services checks and
I have run into a problem that I have been unable 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
2011 Mar 11
9
Why is it so hard to make a sane nagios server config?
I''ve tried to achieve my overall goals with several different features
of Puppet, but I''ve hit a bit of a wall here. I think it''s time for me
to explain what I''m trying to accomplish:
I want the enabling of a service in my manifests to configure
the monitoring of that service by a nagios server, without
needless repetition.
Let me explain how my
2011 Sep 29
2
Naginator and Puppet on different hosts
We were using Naginator resources like nagios_host, etc. along with stored configurations and exported resources. Worked pretty well. However we have to separate the Puppet master and the Icinga (Nagios) server. They will be on different machines from now on. Are there any best practices for such a scenario? I already thought about some kind of ''rsync'' of the configuration from
2008 Nov 19
1
Builtin Nagios types
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I''me using nagios builtin types and I''m very surprised that the
parameter *name* is not available for type nagios_host ?!?
This parameter is required to use inheritance
(http://nagios.sourceforge.net/docs/3_0/objectinheritance.html) and I
don''t understand why it is not included in all nagios types ?
Maybe someone has
2012 Feb 03
3
Interesting permissions issue with nagios_* providers
Hi folks,
I noticed an interesting problem with the nagios_* providers especially in
Debian. Besides writing to the wrong file (I fixed that issue) I''ve
noticed there is a umask issue where the config files end up being owned by
root with perms 0640. This causes nagios to spit milk out of its nose
because it cannot read the configuration files.
I came up with a kludgey solution to the
2011 Apr 04
4
Puppet nagios integration problem
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 =>
2011 Nov 04
1
Storeconfigs and nagios and foreman
All-
Poking around in the bug database it looks like storeconfigs is being
actively worked on. I am using 2.7.6 on my master as well as all the
clients. I have clients boot , start puppet and get a signed cert via
auto signing. The nagios module (and currently the only thing puppet
does) complains a lot during compile time about not having
storeconfigs enabled, which is not the case in my