thruk agent #5

Supports: trusty xenial bionic


Exposes thruk interface to nagios


The thruk-agent charm will no longer be maintained by nagios-charmers. If you have this charm installed without a publisher (i.e. "cs:thruk-agent") you do not need to do anything. The charm will automatically update to the new maintainer. If you are referencing "~nagios-charmers/thruk-agent" you will need to update to the new maintainer: "~bootstack-charmers/thruk-agent" (


This charm is intended to enable a Thruk( web interface to a Nagios unit. Essentially, it enables the Nagios unit to be consolidated into a Thruk view using a thruk-master charm. You can use the local thruk directly, but it is not the intended use of the charm.


juju deploy nagios
juju deploy thruk-agent
juju deploy thruk-master
juju add-relation nagios thruk-agent
juju add-relation thruk-master thruk-agent

You should be able to go to http:///thruk/ and see the webui.


There are a handful of config options

  • source - the PPA to install Thruk from

  • nagios_context - the identifying string for this nagios instance

  • livestatus_path - the path to the livestatus socket

Contact Information


(string) Key ID to import to the apt keyring to support use with arbitary source configuration from outside of Launchpad archives or PPA's.
(string) Path to livestatus socket
(string) Used by the nrpe-external-master subordinate charm. 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) Optional configuration to support use of additional sources such as: - ppa:myteam/ppa - cloud:trusty-proposed/kilo - main The last option should be used in conjunction with the key configuration option.