As part of Performance Monitoring integration with tripleo we have a collectd-environment.yaml installed on the undercloud node. This file is missing parameter description so user don't have a clue what parameters should be there. Check github for the parameters. https://github.com/openstack/tripleo-heat-templates/blob/master/puppet/services/metrics/collectd.yaml#L45,L50
There is an upstream review for this @ https://review.openstack.org/#/c/440759/1
The patch https://review.openstack.org/#/c/440759 is merged
Test instructions: verify that /usr/share/openstack-tripleo-heat-templates/environments/collectd-environment.yaml has a verbose documentation of parameters.
fixed. ------- collectd-environment.yaml looks like this: resource_registry: OS::TripleO::Services::Collectd: ../puppet/services/metrics/collectd.yaml # parameter_defaults: # ## Collectd server configuration # CollectdServer: collectd0.example.com # ################ #### Other config parameters, the values shown here are the defaults ################ # # CollectdServerPort: 25826 # CollectdSecurityLevel: None # ################ #### If CollectdSecurityLevel is set to Encrypt or Sign #### the following parameters are also needed ############### # # CollectdUsername: user # CollectdPassword: password # ## CollectdDefaultPlugins, These are the default plugins used by collectd # # CollectdDefaultPlugins: # - disk # - interface # - load # - memory # - processes # - tcpconns # ## Extra plugins can be enabled by the CollectdExtraPlugins parameter: ## All the plugins availables are: # # CollectdExtraPlugins: # - disk # - df # ## You can use ExtraConfig (or one of the related *ExtraConfig keys) ## to configure collectd. See the documentation for puppet-collectd at ## https://github.com/voxpupuli/puppet-collectd for details. # # ExtraConfig: # collectd::plugin::disk::disks: # - "/^[vhs]d[a-f][0-9]?$/" # collectd::plugin::df::mountpoints: # - "/" # collectd::plugin::df::ignoreselected: false # collectd::plugin::cpu::valuespercentage: true
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2721