Healthwatch v2.2+ requires OpsMan to be set with FQDN

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

Healthwatch V2.2 is now automatically configuring Grafana root URL.

Previously for Healthwatch v2.1, users had to manually configure the DNS record for the Grafana instance to allow access to the Grafana UI, and had to manually configure the root URL in the Grafana UI in the Grafana root URL field. Healthwatch v2.2 can automatically configure a DNS record for the Grafana VM if TAS is installed. It is done by using the Gorouter in TAS and the domain for system-level TAS components: https://grafana.SYSTEM-DOMAIN

Configuring UAA authentication for the Grafana UI was also a manual process, which required creating a UAA client for the Grafana instance and configuring the UAA client in Healthwatch. When you select UAA as your Grafana UI authentication method in the Grafana Authentication pane of the Healthwatch v2.2 tile, Healthwatch can automatically configure authentication with the UAA instances in TAS for the Grafana UI. It automatically does this by using the URL of the UAA instance to targeting the UAA server for TAS. This URL is usually https://login.SYSTEM-DOMAIN, where SYSTEM-DOMAIN is the domain you configured in the System domain field in the Domains pane of the TAS tile.

Environment

Product Version: 2.1

Resolution

If the OpsMan is setup with hostname instead of FQDN, the grafana fails to resolve the hostname, hence the OpsMan has to have an FQDN.
This KB is useful in configuring FQDN