collectd

  • By jacekn
  • Latest version (#0)
  • trusty
  • Stable
  • Edge

Description

collectd is a small daemon which collects system information
periodically and provides mechanisms to monitor and store the values
in a variety of ways. Since the daemon doesn't need to startup every
time it wants to update the values it's very fast and easy on the
system. Also, the statistics are very fine grained since the files are
updated every 10 seconds by default. The collected information can be
used to find current performance bottlenecks (performance analysis)
and predict future system load (capacity planning).


Branch code:
$JUJU_REPOSITORY/layers/collectd/

Assemble the charm:
charm compose

And deploy:
juju deploy local:trusty/collectd

Configuration

nagios_servicegroups
(string) Comma separated list of nagios servicegroups for the graphite check
juju
graphite_protocol
(string) TCP or UDP. Only used if graphite_endpoint is set
TCP
nagios_context
(string) 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.
juju
graphite_prefix
(string) Prepended to unit hostname in graphite. Only used in graphite_endpoint is set
collectd.
graphite_endpoint
(string) Optional graphite hostname(or IP) and port. For example: graphite.example.com:2003 If set write_graphite will be enabled and configured
interval
(int) Interval at which to query values by default
10
prometheus_export
(string) If set collectd will be configured to publish metrics to prometheus graphite_exporter service using write_http plugin. If host is set to 127.0.0.1 the charm will install collectd_exporter package which must be available for installation. See "install_sources" and "install_keys". Please note that it is also possible to send metric to remote collectd_exporter using collectd binary protocol. This can be done using "network_target" option. Examples: To send metrics to remote collectd_exporter instance using http POST to "/my-post-url": http://remote.host.example.com:9103/my-post-url To install collectd_exporter locally and expose metrics for prometheus scraping under "/metrics" URI set this option to: http://127.0.0.1:9103/metrics
network_target
(string) Configured collectd to send data over network to remote collectd intance. Example: 192.168.99.99:25826
plugins
(string) Comma separated list of plugins to enable. If set to "default" list of plugins will match defaults shipped with Ubuntu package
default
install_keys
(string) YAML list of GPG keys for installation sources, as a string. For apt repository URLs, use the public key ID used to verify package signatures. For other sources such as PPA, use empty string. This list must have the same number of elements as install_sources, even if the key items are all empty string. An example to go with the above for install_sources: install_keys: | - "" - ""
install_sources
(string) YAML list of additional installation sources, as a string. The number of install_sources must match the number of install_keys. For example: install_sources: | - ppa:project1/ppa - ppa:project2/ppa