Forge Home


Synchronizes Opsview monitoring tool configuration


6,573 latest version

3.6 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.6.0 (latest)
  • 0.0.1 (deleted)
released Jul 21st 2016

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'opsview-opsview', '0.6.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add opsview-opsview
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install opsview-opsview --version 0.6.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



opsview/opsview — version 0.6.0 Jul 21st 2016

Stable release download

If you're looking for stable releases, you can download this module at the Puppet Forge.


Right now, the module only contains libraries to handle all of the REST requests to a given Opsview server. You will need to create /etc/puppet/opsview.conf with the following format on each client that you wish to connect with an Opsview server:

username: foobar
password: foobaz

Please file bugs via the issue tracker above.


  • Puppet (of course :)) Tested most recently with puppet 2.7.9
  • rest-client, json gems.

Puppet Types in this Module

  • opsview_attribute
  • opsview_bsmcomponent
  • opsview_bsmservice
  • opsview_contact
  • opsview_hostgroup
  • opsview_hosttemplate
  • opsview_keyword
  • opsview_monitored
  • opsview_monitoringserver
  • opsview_notificationmethod
  • opsview_role
  • opsview_servicecheck
  • opsview_servicegroup
  • opsview_tenancy

List of things to do

  1. Separate out a few get/set methods from Puppet::Provider::Opsview - put them in a utility module instead.

  2. Clean up Puppet::Provider::Opsview in general. Cull any class/instance methods we don't need (there's lots of duplication.)

  3. Add default providers so that Puppet runs don't fail when there's no rest-client / json gems to use.