contrail service checks #4

Supports: bionic


This charm provides Contrail service checks for Nagios


The goal of this charm is to provide NRPE checks for Contrail. It will pull the alarms from Contrail analytics. If an alarm is found, a CRITICAL response is sent to NRPE. If no alarm is found, an OK response is sent to NRPE.


# Assuming that a working Contrail + OpenStack environment is already deployed with Nagios and NRPE
juju deploy cs:~npochet/contrail-service-checks
juju config contrail-service-checks contrail_analytics_vip=VIP
juju add-relation nrpe contrail-service-checks
juju add-relation keystone contrail-service-checks

Scale out Usage

There is no use to scale this charm.

Known Limitations and Issues

  • No scale out
  • Not tested against a cloud with HTTPS for Keystone
  • Basic checks of the Contrail alarms:
  • If there's any alarm -> CRITICAL
  • If there's no alarm -> OK
  • In any case, print the result of the query


(string) The VIP used for Contrail Analytics
(string) Used by the nrpe subordinate charms. A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.
(string) A comma-separated list of nagios servicegroups. If left empty, the nagios_context will be used as the servicegroup
(string) Comma separated OpenStack credentials to be used by nagios. It is strongly recommended this be a user with a dedicated role, and not a full admin. Takes the format of username=foo, password=bar, project_name=baz, region_name=Region1, auth_url=
(string) base64 encoded SSL ca cert to use for OpenStack API client connections.