Skip to content
A Puppet report processor that announces failed runs to HipChat
Ruby Puppet HTML
Fetching latest commit…
Cannot retrieve the latest commit at this time.



A Puppet report handler for sending notifications of Puppet runs to HipChat.

TravisCI status

Build Status


  • hipchat >= 0.12.0
  • puppet


NOTE FOR OPEN SOURCE PUPPET 3 USERS: The Hipchat gem requires ruby >= 1.9.3 this does not apply to Puppet Enterprise and AIO / Puppet4 installations which provide their own ruby installation > 1.9.3

  1. Install the hipchat gem on your Puppet master

    $ sudo gem install hipchat

NOTE FOR PUPPET ENTERPRISE USERS: You must install the hipchat gem using the puppet-bundled gem library:

    $ /opt/puppet/bin/gem install hipchat

NOTE FOR AIO package 2.0.0+ USERS: You must install the hipchat gem using the puppetserver gem utility:

    $ /opt/puppetlabs/bin/puppetserver gem install hipchat
  1. Install puppet-hipchat as a module in your Puppet master's module path.

  2. Create a HipChat API key here with a type of Admin. Record the API key that is generated.

    Alternitively if you are using an on premise hipchat installation, generate an integration key.

  3. Update the hipchat_api and hipchat_room variables in the hipchat.yaml file with your Hipchat connection details and copy the file to /etc/puppet/ or for Puppet Enterpise and AIO 2.0.0+ /etc/puppetlabs/puppet.

    If you are using an on premise hipchat installation, also update hipchat_server with the url to the hipchat server.

  4. Enable pluginsync and reports on your master and clients in puppet.conf

    report = true
    reports = hipchat
    pluginsync = true
    report = true
    pluginsync = true
  5. Run the Puppet client and sync the report as a plugin


  • An option to notify users in the room hipchat_notify defaults to false.

  • You can also change the default notification color from yellow to red, green, purple or random.

  • The hipchat_statuses should be an array of statuses to send notifications for and defaults to 'failed'. Specify 'all' to receive notifications from all Puppet runs.

  • In order to send notifications through proxy server set hipchat_proxy to your HTTP proxy URL using this format:


  • If you use Puppetboard set hipchat_puppetboard to the base URL of your Puppetboard installation, e.g. '' and a link to the node's latest report will be send with the message to HipChat. An example file is included.

    NOTE FOR PUPPETBOARD 0.1.2+ USERS: if you are using environments other than production you will need to either configure puppetboard default environment to * or set hipchat_server to append /%2A, ex: :hipchat_server: http://hipchat.test.local/%2A otherwise you will receive a not found error for nodes in environments which are not production.

  • To temporarily disable HipChat notifications add a file named hipchat_disabled in the same path as hipchat.yaml. Removing it will re-enable notifications.

    $ touch /etc/puppet/hipchat_disabled

  • Modern hipchat installations may not support the default v1 api set hipchat_api_version to v2 for modern api support.


Maintainer: James Powis

Original author: James Turnbull


Author:: James Turnbull (<>)
Copyright:: Copyright (c) 2011 James Turnbull
License:: Apache License, Version 2.0

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
See the License for the specific language governing permissions and
limitations under the License.
Something went wrong with that request. Please try again.