You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 1, 2023. It is now read-only.
@@ -68,8 +65,6 @@ class { 'puppet_metrics_dashboard':
68
65
69
66
```
70
67
class { 'puppet_metrics_dashboard':
71
-
configure_telegraf => true,
72
-
enable_telegraf => true,
73
68
master_list => ['master1.com',
74
69
# Alternate ports may be configured using
75
70
# a pair of: [hostname, port_number]
@@ -81,11 +76,11 @@ class { 'puppet_metrics_dashboard':
81
76
82
77
### Allow access to PE-managed postgres nodes with the following class:
83
78
84
-
This is required for collection of postgres metrics.
79
+
This is required for collection of postgres metrics. The class should be applied to the master (or postgres server if using external postgres).
85
80
86
81
```
87
82
class { 'puppet_metrics_dashboard::profile::postgres':
88
-
grafana_host => 'postgres01',
83
+
grafana_host => 'grafana-server.example.com',
89
84
}
90
85
```
91
86
@@ -102,17 +97,15 @@ class { 'puppet_metrics_dashboard':
102
97
}
103
98
```
104
99
105
-
* This method requires enabling on the master side as described [here](https://puppet.com/docs/pe/2017.3/puppet_server_metrics/getting_started_with_graphite.html#enabling-puppet-server-graphite-support). The hostname(s) that you use in `master_list` should match the value(s) that you used for `metrics_server_id` in the `puppet_enterprise::profile::master` class.
100
+
* This method requires enabling on the master side as described [here](https://puppet.com/docs/pe/2017.3/puppet_server_metrics/getting_started_with_graphite.html#enabling-puppet-server-graphite-support). The hostname(s) that you use in `master_list` should match the value(s) that you used for `metrics_server_id` in the `puppet_enterprise::profile::master` class.
106
101
107
-
### Enable Telegraf, Graphite, and Archive
102
+
### Enable Telegraf, Graphite, and Archive (puppet_metrics)
@@ -130,14 +123,41 @@ By default, this will create a set of certificates in `/etc/grafana` that are ba
130
123
131
124
_Note:_ Enabling SSL on Grafana will not allow for running on privileged ports such as `443`. To enable this capability you can use the suggestions documented in [this Grafana documentation](http://docs.grafana.org/installation/configuration/#http-port)
132
125
126
+
### Profile defined types
127
+
128
+
The module includes defined types that you can use with an existing grafana implementation. For example:
Configure the passwords for the InfluxDB and Grafana administrator users and enable additional [TICK Stack](https://www.influxdata.com/time-series-platform/) components.
156
+
Configure the passwords for the InfluxDB and enable additional [TICK Stack](https://www.influxdata.com/time-series-platform/) components.
136
157
137
158
```
138
159
class { 'puppet_metrics_dashboard':
139
160
influx_db_password => 'secret',
140
-
grafana_password => 'secret',
141
161
grafana_http_port => 8080,
142
162
grafana_version => '4.5.2',
143
163
enable_chronograf => true,
@@ -147,7 +167,7 @@ class { 'puppet_metrics_dashboard':
147
167
148
168
## Reference
149
169
150
-
**Note** This section is no longer maintained. Please see the REFERENCE.MD file for current listings.
170
+
**Note** This section is no longer maintained. Please see the REFERENCE.MD file for current listings.
151
171
152
172
## Limitations
153
173
@@ -159,7 +179,7 @@ Error: Execution of '/usr/bin/yum -d 0 -e 0 -y install telegraf' returned 1: Err
159
179
Error: /Stage[main]/Pe_metrics_dashboard::Telegraf/Package[telegraf]/ensure: change from purged to present failed: Execution of '/usr/bin/yum -d 0 -e 0 -y install telegraf' returned 1: Error: Cannot retrieve repository metadata (repomd.xml) for repository: influxdb. Please verify its path and try again
160
180
```
161
181
162
-
To recify the issue, please update `nss` and `curl` on the affected system.
182
+
To rectify the issue, please update `nss` and `curl` on the affected system.
0 commit comments