-
Notifications
You must be signed in to change notification settings - Fork 40
Conversation
templates/telegraf.conf.epp
Outdated
| <% if $postgres_host {-%> | ||
|
|
||
| [[inputs.postgresql_extensible]] | ||
| address = "postgres://telegraf@<%= $postgres_host %>/pe-puppetdb?sslmode=require&sslkey=/etc/telegraf/<%= $fqdn %>.private_key.pem&sslcert=/etc/telegraf/<%= $fqdn %>.public_key.pem&sslrootcert=/etc/telegraf/ca.pem" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The two $fqdn entries here do not correspond to any parameters being passed into this template per the section at the top of the file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah this is doing the legacy fact thing again. Can we use $facts['networking']['fqdn'] or does the parameter have to be passed in?
|
|
||
| [[inputs.postgresql_extensible]] | ||
| address = "postgres://telegraf@<%= $postgres_host %>/pe-puppetdb?sslmode=require&sslkey=/etc/telegraf/<%= $fqdn %>.private_key.pem&sslcert=/etc/telegraf/<%= $fqdn %>.public_key.pem&sslrootcert=/etc/telegraf/ca.pem" | ||
| databases = ["pe-puppetdb","pe-rbac","pe-activity","pe-classifier"] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be adjusted to work with FOSS puppet too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly, we'd also need a different profile class to setup access on the master side, since the PR as-is leverages PE modules.
This will add the ability to monitor the PE postgres database and setup an example dashboard.