HipSaint
==========
Push your nagios notifications to HipChat using a simple command line tool.
.. image:: https://travis-ci.org/hannseman/hipsaint.png?branch=master
:target: https://travis-ci.org/hannseman/hipsaint
.. image:: https://img.shields.io/pypi/dm/hipsaint.svg
:target: https://pypi.python.org/pypi/hipsaint
Implements `HipChat message API`_.
.. _`hipchat message API`: https://www.hipchat.com/docs/api/method/rooms/message
Inspired by https://gist.github.com/2418848.
---------
Install
---------
Through pip:
.. code-block:: bash
pip install hipsaint
Or clone and simply run:
.. code-block:: bash
python setup.py install
-------
Usage in Nagios
-------
Assuming you use Nagios 3 add the following sections to commands.cfg with ``<TOKEN>`` and ``<ROOM_ID>`` specified and macros delimited by ``|``::
define command {
command_name notify-host-by-hipchat
command_line hipsaint -V 2 --token=<TOKEN> --room=<ROOM_ID> --type=host --inputs="$HOSTNAME$|$LONGDATETIME$|$NOTIFICATIONTYPE$|$HOSTADDRESS$|$HOSTSTATE$|$HOSTOUTPUT$" -n
}
define command {
command_name notify-service-by-hipchat
command_line hipsaint -V 2 --token=<TOKEN> --room=<ROOM_ID> --type=service --inputs="$SERVICEDESC$|$HOSTALIAS$|$LONGDATETIME$|$NOTIFICATIONTYPE$|$HOSTADDRESS$|$SERVICESTATE$|$SERVICEOUTPUT$" -n
}
To send less verbose messages to hipchat set the ``--type`` flag to either ``short-host`` or ``short-service``.
Additional commands is available through:
.. code-block:: bash
hipsaint --help
Edit the Nagios contacts.cfg file by adding or editing an existing user and adding the notification commands created above::
define contact {
....
.....
service_notification_commands notify-service-by-hipchat
host_notification_commands notify-host-by-hipchat
email /dev/null
}
-------
Usage in Icinga 2
-------
To use Hipsaint in Icinga 2, you can create an additional config like this :
Create two scripts, one for hosts, one for services :
Don't forget to fill ``<TOKEN>`` and ``<ROOM_ID>``.
Hosts : /etc/icinga2/scripts/hipchat-host-notification.sh ::
#!/bin/bash
hipsaint --user=Icinga --token=<TOKEN> --room=<ROOM_ID> --type=host --inputs="$HOSTNAME|$LONGDATETIME|$NOTIFICATIONTYPE|$HOSTADDRESS|$HOSTSTATE|$HOSTOUTPUT" -n
or
hipsaint -V 2 --token=<TOKEN> --room=<ROOM_ID> --type=host --inputs="$HOSTNAME|$LONGDATETIME|$NOTIFICATIONTYPE|$HOSTADDRESS|$HOSTSTATE|$HOSTOUTPUT" -n
Services : /etc/icinga2/scripts/hipchat-service-notification.sh ::
#!/bin/bash
hipsaint --user=Icinga --token=<TOKEN> --room=<ROOM_ID> --type=service --inputs="$SERVICEDESC|$HOSTALIAS|$LONGDATETIME|$NOTIFICATIONTYPE|$HOSTADDRESS|$SERVICESTATE|$SERVICEOUTPUT" -n
or
hipsaint -V 2 --token=<TOKEN> --room=<ROOM_ID> --type=service --inputs="$SERVICEDESC|$HOSTALIAS|$LONGDATETIME|$NOTIFICATIONTYPE|$HOSTADDRESS|$SERVICESTATE|$SERVICEOUTPUT" -n
Then you need to tell Icinga to use those scripts :
Create a file called ``hipsaint.conf`` in your ``conf.d`` directory ::
/**
* Hipchat/Hipsaint script for Icinga2
*
* Only applied if host/service objects have
* the custom attribute `sla` set to `24x7`.
*/
object NotificationCommand "notify-host-by-hipchat" {
import "plugin-notification-command"
command = [ "/etc/icinga2/scripts/hipchat-host-notification.sh" ]
env = {
HOSTNAME = "$host.name$"
LONGDATETIME = "$icinga.long_date_time$"
NOTIFICATIONTYPE = "$notification.type$"
HOSTADDRESS = "$address$"
HOSTSTATE = "$host.state$"
HOSTOUTPUT = "$host.output$"
}
}
object NotificationCommand "notify-service-by-hipchat" {
import "plugin-notification-command"
command = [ "/etc/icinga2/scripts/hipchat-service-notification.sh" ]
env = {
SERVICEDESC = "$service.name$"
HOSTALIAS = "$host.display_name$"
LONGDATETIME = "$icinga.long_date_time$"
NOTIFICATIONTYPE = "$notification.type$"
HOSTADDRESS = "$address$"
SERVICESTATE = "$service.state$"
SERVICEOUTPUT = "$service.output$"
}
}
apply Notification "hipchat-icingaadmin" to Host {
command = "notify-host-by-hipchat"
user_groups = [ "icingaadmins" ]
assign where host.vars.sla == "24x7"
}
apply Notification "hipchat-icingaadmin" to Service {
command = "notify-service-by-hipchat"
user_groups = [ "icingaadmins" ]
assign where service.vars.sla == "24x7"
}
You want to customize this to your groups and users.
Metadata
Release files for hipsaint 0.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| hipsaint-0.7.tar.gz | 6.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hipsaint-0.7-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 15.0 kB
Release files / hipsaint-0.7.tar.gz
| Download URL | hipsaint-0.7.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c3f7a5f45bd432d032a5c9a8a13d8dfc1dde1719489bd30aaf4aa640cfa6862
|
|
BLAKE2b-256 checksum How to use checksums |
d13f7ccb8261c0cdda047cc54e19ce0351cf3d11fdd4971e79db0f4b95d519ac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / hipsaint-0.7-py2.py3-none-any.whl
| Download URL | hipsaint-0.7-py2.py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
2fec5693ff5f7bbdf4d052e11ded1a357881e98b29e62cf681ccceeab927e4b4
|
|
BLAKE2b-256 checksum How to use checksums |
812d53f985b2cee7fcd5c098a16dd0906e224b2f554f81101df5fc951a593ace
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for hipsaint 0.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.