Problem Statement

Here is the link

https://docs.redhat.com/en/documentation/red_hat_satellite/6.15/html-single/monitoring_satellite_performance/index#configuring-pcp-data-collection_monitoring

and here is the recommendation

cd /var/lib/pcp/pmdas/openmetrics
echo "https://satellite.example.com/metrics" > config.d/foreman.url
./Install 

Instead, it could be something like

cd /var/lib/pcp/pmdas/openmetrics
echo "https://$(hostname -f)/metrics" > config.d/foreman.url
./Install 

The reason is because, in general, the customer will copy/paste the command and will move on, as consequence, the implementation will fail, once the FQDN is different.

Note that there is no warning about the FQDN to be updated.

Here, we can see using the recommended one and the new one

By doc

[root@wallsat615]# echo "https://satellite.example.com/metrics" > config.d/foreman.url
[root@wallsat615]# cat config.d/foreman.url
https://satellite.example.com/metrics 

Suggested on this Jira

[root@wallsat615 ]# echo "https://$(hostname -f)/metrics" > config.d/foreman.url
[root@wallsat615 ]# cat config.d/foreman.url
https://wallsat615.d.sysmgmt.cee.redhat.com/metrics 

User Experience & Workflow

[Describe the experience/interaction/steps of this request as a workflow
with expected outcomes at each step. What is the end-state and how will
they be able to verify a successful outcome?]

Requirements

[A list of specific needs or objectives that a Feature must deliver to
satisfy the Feature. Note: Any requirements that are not flagged as MVP,
should be evaluated and considered for another feature.]

Business Impact

[What would happen if the inclusion of this feature wasn’t undertaken?
Would any projects at Red Hat be negatively affected?]