This repository has been archived by the owner on Jun 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 40
Port numbers for monitored services monitored by should be configurable #48
Labels
enhancement
New feature or request
Comments
I'm thinking the easiest way to implement this would be to change the dataype of the host lists from
|
Sharpie
added a commit
to Sharpie/puppet_metrics_dashboard
that referenced
this issue
Apr 25, 2019
This commit updates the master_list, puppetdb_list, and postgres_host_list parameters to allow pairs of `[hostname, port number]` in addition to just a hostname. If the port number is specified, then Telegraf will be configured to use that port when requesting metrics from the host. If no port number is specified, then Telegraf will be configured to use the default prts of 8140 for Puppet Server, 8081 for PuppetDB, and 5432 for Postgres. Closes puppetlabs#48
Sharpie
added a commit
to Sharpie/puppet_metrics_dashboard
that referenced
this issue
Apr 25, 2019
This commit updates the master_list, puppetdb_list, and postgres_host_list parameters to allow pairs of `[hostname, port_number]` in addition to just a hostname. If the port number is specified, then Telegraf will be configured to use that port when requesting metrics from the host. If no port number is specified, then Telegraf will be configured to use the default prts of 8140 for Puppet Server, 8081 for PuppetDB, and 5432 for Postgres. Closes puppetlabs#48
Sharpie
added a commit
to Sharpie/puppet_metrics_dashboard
that referenced
this issue
Apr 25, 2019
This commit updates the master_list, puppetdb_list, and postgres_host_list parameters to allow pairs of `[hostname, port_number]` in addition to just a hostname. If the port number is specified, then Telegraf will be configured to use that port when requesting metrics from the host. If no port number is specified, then Telegraf will be configured to use the default prts of 8140 for Puppet Server, 8081 for PuppetDB, and 5432 for Postgres. Closes puppetlabs#48
Sharpie
added a commit
to Sharpie/puppet_metrics_dashboard
that referenced
this issue
Apr 25, 2019
This commit updates the master_list, puppetdb_list, and postgres_host_list parameters to allow pairs of `[hostname, port_number]` in addition to just a hostname. If the port number is specified, then Telegraf will be configured to use that port when requesting metrics from the host. If no port number is specified, then Telegraf will be configured to use the default prts of 8140 for Puppet Server, 8081 for PuppetDB, and 5432 for Postgres. Closes puppetlabs#48
Sharpie
added a commit
to Sharpie/puppet_metrics_dashboard
that referenced
this issue
Apr 25, 2019
This commit updates the master_list, puppetdb_list, and postgres_host_list parameters to allow pairs of `[hostname, port_number]` in addition to just a hostname. If the port number is specified, then Telegraf will be configured to use that port when requesting metrics from the host. If no port number is specified, then Telegraf will be configured to use the default prts of 8140 for Puppet Server, 8081 for PuppetDB, and 5432 for Postgres. Closes puppetlabs#48
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
telegraf.conf.epp
template currently hardcodes the ports that it uses to collect data from monitored services, 8140, 8081. The Postgres collection also omits the port number, which is an equivalent to harcoding 5432.PuppetDB commonly has to run on a different port as 8081 conflicts with several monitoring and anti-virus products. We should make the port numbers configurable.
The text was updated successfully, but these errors were encountered: