1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
<!--
title: "Puppet monitoring with Netdata"
custom_edit_url: https://github.com/netdata/netdata/edit/master/collectors/python.d.plugin/puppet/README.md
sidebar_label: "Puppet"
-->
# Puppet monitoring with Netdata
Monitor status of Puppet Server and Puppet DB.
Following charts are drawn:
1. **JVM Heap**
- committed (allocated from OS)
- used (actual use)
2. **JVM Non-Heap**
- committed (allocated from OS)
- used (actual use)
3. **CPU Usage**
- execution
- GC (taken by garbage collection)
4. **File Descriptors**
- max
- used
## Configuration
Edit the `python.d/puppet.conf` configuration file using `edit-config` from the Netdata [config
directory](/docs/configure/nodes.md), which is typically at `/etc/netdata`.
```bash
cd /etc/netdata # Replace this path with your Netdata config directory, if different
sudo ./edit-config python.d/puppet.conf
```
```yaml
puppetdb:
url: 'https://fqdn.example.com:8081'
tls_cert_file: /path/to/client.crt
tls_key_file: /path/to/client.key
autodetection_retry: 1
puppetserver:
url: 'https://fqdn.example.com:8140'
autodetection_retry: 1
```
When no configuration is given, module uses `https://fqdn.example.com:8140`.
### notes
- Exact Fully Qualified Domain Name of the node should be used.
- Usually Puppet Server/DB startup time is VERY long. So, there should
be quite reasonable retry count.
- Secure PuppetDB config may require client certificate. Not applies
to default PuppetDB configuration though.
---
|
