You can get values from /var/lib/puppet/state/last_run_summary.yaml
We created facts from parsing this yaml and then just getting this fact
with user script.
We use this to get nodes with failures and always running nodes
(nonidepotent).
cat /etc/zabbix/conf.d/zab_puppet.conf
Hi,
I am working on making our puppet infrastructure more dynamic where I can
add any number of nodes and these will automatically be applied in another
nodes configuration.
*An example:*
I have X number of hosts running a Java application, which are defined by
our *javaapp* module with the
Thanks Eric
> This should be /etc/puppetlabs/code/files ...
Oops, sorry for the noise
Cheers
Kashif
On Monday, 11 January 2016 09:57:34 UTC, kashif wrote:
>
> Hi
>
> Is serving files from custom mount point depreciated in puppet 4? I
> configured fileserver.conf file in same way as in
Am Donnerstag, 10. Dezember 2015 16:10:24 UTC+1 schrieb hoize:
>
> Hello!
>
> Is there a way to monitor puppet runs with zabbix?
> Here is what i want to monitor:
> - a host's puppet run is more than 20 minutes ago
>
not related but interesting: why you are running puppet that often?
> - a
Hello,
thank you for your reply!
We often have many changes which are automatically done, so we need to run
puppet that often.
I thougt about this way yet, because we are using Zabbix-Agent
UserParameters. But -honestly- I don't know how to realise this and I'm
actually not able to write a
On 01/19/2016 02:52 AM, Jakov Sosic wrote:
Hi guys,
I've noticed the following problem with one of my providers in v4.
This is the original prefetch method I used:
def self.prefetch(resources)
instances.each do |prov|
if resource = resources[prov[:name]]
Hi guys,
I've noticed the following problem with one of my providers in v4.
This is the original prefetch method I used:
def self.prefetch(resources)
instances.each do |prov|
if resource = resources[prov[:name]]
resource.provider = prov
+resource.provider =
