Welcome to the Pandora FMS Module Library

This is a library with modules, documentation and tools for Pandora FMS users, both public Open Source and Enterprise. Please use your support credentials (same as used to enter support/ticketing system) in the menu to your right. You will be granted access to a resourceful module library, such as Oracle, VMware, JBoss and others, ready to be used in production enviroments, with official professional support from Artica. If you do not own an enterprise account, you still can browse and download lots of modules, you can even register a free account and contribute with your own modules/tools for other public users.

Home > Application monitoring

Puppet plugin

Author: axel Create in: 01/31/2014 Update in: 04/25/2014
Module type : Agent plugin

Plugin for monitoring Puppet agents.

It needs one parameter:
--summary-file: The "last_run_summary.yaml" file.

* Installing pandora's agent
* Installing puppet's agent
* Copy the plugin to the machine you want to monitor

To apply the monitorization:
Add this line to the /etc/pandora/pandora_agent.conf replacing the variables:

module_plugin <path_to_your_plugin>/pandora_puppet.rb <path_to_your_last_run_summary.yaml_file>/last_run_summary.yaml

In CentOS, the last_run_summary.yaml was in the /var/lib/puppet/state directory.

Add this line to the /etc/pandora/pandora_agent.conf replacing the variables:

module_plugin "%programfiles(x86)%\Puppet Labs\Puppet Enterprise\sys\ruby\bin\ruby.exe" <path_to_your_plugin>\pandora_puppet.rb --summary-file <path_to_your_last_run_summary.yaml_file>\last_run_summary.yaml

In Windows, the last_run_summary.yaml was in the C:\ProgramData\PuppetLabs\puppet\var\state directory.

Module data

* Last run
* Time since last run
* Is out of sync?
* Resources changed/failed/failed to restart/restarted/scheduled/skipped
* Events failed/succeeded
*Total changes

Included files