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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,17 @@
2
2
3
3
All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](http://semver.org).
@@ -221,6 +222,72 @@ The easiest way to get started using this module is by including the `puppet_ope
221
222
include puppet_operational_dashboards
222
223
```
223
224
225
+
#### Advanced Telegraf Configuration
226
+
227
+
If you already have an existing setup and defined configuration for Telegraf and InfluxDB, it is possible to only configure the Telegraf inputs needed for collection of Puppet metrics via the `puppet_operational_dashboards::telegraf::agent` class. The main use case for this is if you already manage Telegraf and InfluxDB in Puppet code, and you only want to use this module to collect and ship Puppet metrics to your existing InfluxDB. To do so, you may apply the `puppet_operational_dashboards::telegraf::agent` class to either:
228
+
229
+
* Each Puppet infrastructure node to collect metrics locally
230
+
* A single node to remotely collect metrics from all infrastructure nodes
231
+
232
+
For the first case of local collection, set `collection_method: 'local'` and `local_services` to an array of Puppet services to collect from, for example `local_services: ['puppetserver', 'puppetdb']`.
233
+
234
+
For the second case of remote collection, use `collection_method: 'all'` and set each of the following as needed:
235
+
236
+
* puppetserver_hosts
237
+
* orchestrator_hosts
238
+
* puppetdb_hosts
239
+
* postgres_hosts
240
+
241
+
In either case, you can control whether this class will manage the Telegraf class and service with:
You may also pass additional options to the Telegraf inputs, for example, if you need to add a tag. The following hiera data will add an additional `[inputs.http.tags]` element with a key/value pair of `foo = bar`:
Copy file name to clipboardExpand all lines: functions/pe_profiles_on_host.pp
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,12 @@ function puppet_operational_dashboards::pe_profiles_on_host() >> Array[String] {
10
10
$hosts = puppetdb_query("resources[title] {
11
11
type = 'Class' and
12
12
certname = '${trusted['certname']}' and
13
-
title in ['Puppet_enterprise::Profile::Puppetdb', 'Puppet_enterprise::Profile::Master', 'Puppet_enterprise::Profile::Database', 'Puppet_enterprise::Profile::Orchestrator'] and
0 commit comments