Bug 1845014

https://review.opendev.org/#/c/742685/

memcached is still reporting it by IP address. Moving back to Assign

This can be fixed by adding the following to the stf-connectors.yml:

```
    ExtraConfig:
      collectd::plugin::memcached::instances:
        local:
          host: "%{hiera('fqdn_canonical')}
          port: 11211
```

Hi Joanne,

Originally I figured this would go in the dashboard section, but I think it would be better to be upfront about the change. The section you pointed out would be better IMO.

We can add a bullet point that goes as follows:

- In the ExtraConfig, add the following to tell the collectd memcached to report the hostname by fqdn rather than ip address in accordance with the rest of the collectd plugins:

>       collectd::plugin::memcached::instances:
>         local:
>           host: "%{hiera('fqdn_canonical')}
>           port: 11211

And then below, where the whole stf-connectors.yaml is laid out, also include the changes:

> parameter_defaults: 
>     EventPipelinePublishers: []
>     PipelinePublishers: []
>     CeilometerQdrPublishEvents: true
>     CeilometerQdrPublishMetrics: true
>     MetricsQdrConnectors:
>     - host: default-interconnect-5671-service-telemetry.apps.infra.watch
>       port: 443
>       role: edge
>       sslProfile: sslProfile
>       verifyHostname: false
>     ExtraConfig:
>       ceilometer::agent::polling::polling_interval: 5
>       collectd::plugin::memcached::instances:
>         local:
>           host: "%{hiera('fqdn_canonical')}
>           port: 11211

This issue will be solved by updates to our enable-stf.yaml and will no longer need a documentation update: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/795608/4/environments/enable-stf.yaml

(In reply to Paul Leimer from comment #15)
> This issue will be solved by updates to our enable-stf.yaml and will no
> longer need a documentation update:
> https://review.opendev.org/c/openstack/tripleo-heat-templates/+/795608/4/
> environments/enable-stf.yaml

Actually I think we'll need to include this in the docs in the short term. I think the way this will go will be:

1) change as you've described here

2) migrate to documenting the enable-stf.yaml and changing the installation procedure slightly, with a copy/pasta of the new enable-stf.yaml

3) once changes are available in the downstream product, refer to the in-tree enable-stf.yaml and remove the documented copy/pasta method

This has been addressed in the `enable-stf.yaml` (base config) in the STF 1.3 documentation. See https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html/service_telemetry_framework_1.3/assembly-completing-the-stf-configuration_assembly#creating-the-base-configuration-for-stf_assembly-completing-the-stf-configuration