It is very common for PuppetDB installs to run on a different host than
the puppetmaster. In such cases, a certificate file is normally used to
establish an encrypted communication to the server.
The most common setup for this server certificate is to use a
certificate that was signed by the puppetmaster's CA, so one would want
to verify the server cert against this same CA (it should be present on
puppet clients).
Moreover, to ensure that *only* puppet clients can communicate with
PuppetDB, a pair of client certificat/key files are usually used to
authenticate clients.
PuppetDB requires a pretty high amount of memory allocated to it. If you
don't give enough memory space to the JVM, PuppetDB might crash when it
has fully used the available max memory. This plugin should be useful
for better tuning up your instance(s) of PuppetDB.
Currently, it's only compatible with PuppetDB 6.x since it's requesting
data from the API as described for that version:
https://puppet.com/docs/puppetdb/6.0/api/metrics/v1/mbeans.html#jvm-metrics
To add support for more versions, one would need to consult the same
documentation for different versions and to adapt URLs used and the code
that's obtaining the data from JSON if the layout of the responses is
different.
- "puppetd" and "puppetmasterd" is no longer in use
- The use of "/etc/sysconfig" made this plugin specific for RedHat-ish
systems
- any plugin to replace this should use the "puppet" command to get
configuration, and be implemented as a multigraph plugin.
This closes issue #424
