Upgrading Healthwatch

This topic describes how to upgrade to Healthwatch™ for VMware Tanzu^® v2.2 (Healthwatch).

Overview

Healthwatch v2.2 uses the open-source components Prometheus, Grafana, and Alertmanager to scrape, store, and view metrics, as well as configure alerts. This architecture is entirely different from the architecture of Pivotal Healthwatch v1. Because of this, you must install Healthwatch v2.2 as a new tile.

For more information about the differences between Healthwatch v2.2 and Pivotal Healthwatch v1, see Differences Between Healthwatch v2.2 and Pivotal Healthwatch v1 below.

To upgrade to Healthwatch v2.2 from Pivotal Healthwatch v1, see Upgrade to Healthwatch v2.2 below.

Differences Between Healthwatch v2.2 and Pivotal Healthwatch v1

The following table explains the most significant differences between Healthwatch v2.2 and Pivotal Healthwatch v1:

Feature	Difference Between Versions
Architecture	Healthwatch v2.2: Uses the open-source components Prometheus, Grafana, and Alertmanager to scrape, store, and view metrics, as well as configure alerts. Healthwatch v2.2 deploys multiple Prometheus VMs by default to maintain high availability (HA), and you can scale other Healthwatch components to make them HA. Pivotal Healthwatch v1: Consists of a dashboard and alerting system within the Pivotal Healthwatch v1 tile to monitor metrics and send alerts. If Pivotal Healthwatch v1 components become temporarily unavailable, Pivotal Healthwatch v1 relies on various other Ops Manager tiles to buffer or queue metrics. For more information about the architecture of Healthwatch v2.2, see Healthwatch Architecture.
Metrics	Healthwatch v2.2: Stores metrics in the time-series database (TSDB) on each Prometheus VM either for 42 days or until 85% of persistent disk space is full. Pivotal Healthwatch v1: Stores metrics in MySQL for only 24 hours. For more information about Healthwatch v2.2 metrics, see Healthwatch Metrics.
Alerting	Healthwatch v2.2: Uses Alertmanager, a Prometheus component, to manage and send alerts according to the alerting rules you configure. Pivotal Healthwatch v1: Uses the Pivotal Event Alerts service, through which you can subscribe to alerts for specific events using the Cloud Foundry Command-Line Interface (cf CLI). For more information about configuring alerts, see Configuring Alerting.
Monitoring multiple Ops Manager foundations	Healthwatch v2.2: Can monitor both VMware Tanzu Application Service for VMs (TAS for VMs) and VMware Tanzu Kubernetes Grid Integrated Edition (TKGI), and can monitor multiple Ops Manager foundations with one or both runtimes installed. Pivotal Healthwatch v1: Can only monitor TAS for VMs on a single Ops Manager foundation. For more information about using Healthwatch v2.2 to monitor multiple Ops Manager foundations, see Configuration Options in Healthwatch Architecture.
Platform scope	Healthwatch v2.2: Displays metrics from multiple Ops Manager foundations in the Grafana user interface (UI). Pivotal Healthwatch v1: Displays metrics only from the Ops Manager foundation on which it is installed in the Pivotal Healthwatch v1 tile UI. For more information about using Healthwatch v2.2 to monitor multiple Ops Manager foundations, see Configuration Options in Healthwatch Architecture.
Certificate expiration monitoring	Healthwatch v2.2: Optionally collects metrics that show when certain Ops Manager certificates are due to expire. Pivotal Healthwatch v1: Does not monitor certificate expiration. For more information about monitoring certificates, see Monitoring Certificate Expiration.
Dashboard customization	Healthwatch v2.2: Allows you to customize the default dashboards and create new dashboards in the Grafana UI. Pivotal Healthwatch v1: Does not allow you to edit the dashboard in the Pivotal Healthwatch v1 tile UI. For more information about creating and editing dashboards in the Grafana UI, see the Grafana documentation.
User authentication	Healthwatch v2.2: Can use basic authentication, User Account and Authentication (UAA), OAuth, or LDAP to authenticate users when they log in to the Grafana UI. Pivotal Healthwatch v1: Uses UAA to access the BOSH Director, component metrics, and the Pivotal Healthwatch v1 tile UI. For more information about configuring user authentication for accessing the Grafana UI, see Configuring Grafana Authentication.

In addition to the updated features described in the table above, Healthwatch v2.2 includes the following new features:

Runs a suite of service level indicator (SLI) tests to test the functionality of the TKGI API and collects metrics from those tests in the TKGI Control Plane dashboard in the Grafana UI. For more information, see TKGI SLI Exporter VM in Healthwatch Metrics.
Separates Diego capacity metrics by isolation segment in the Diego/Capacity dashboard in the Grafana UI.
No longer displays metrics from BOSH smoke test deployments in the Jobs and Job Details dashboards in the Grafana UI.
Allows you to include optional dashboards for the VMware Tanzu RabbitMQ for VMs (Tanzu RabbitMQ) and VMware Tanzu SQL with MySQL for VMs (Tanzu SQL for VMs) tiles in the Grafana UI.
Allows you to monitor super value metrics (SVMs) that are similar to the super metrics generated in Pivotal Healthwatch v1.8 and earlier. For more information about SVMs, see Configure Prometheus in Configuring Healthwatch, SVM Forwarder VM - Healthwatch Component Metrics in Healthwatch Metrics, and SVM Forwarder VM - Platform Metrics in Healthwatch Metrics.
Automatically detects which version of TAS for VMs or TKGI is installed on your Ops Manager foundation and creates the appropriate dashboard in the Grafana UI.
Allows you to use the Ops Manager syslog forwarding feature to forward log messages from Healthwatch component VMs to an external destination for troubleshooting, such as a remote server or external syslog aggregation service. For more information about how to configure syslog forwarding, see (Optional) Configure Syslog in Configuring Healthwatch.

For more information about Healthwatch v2.2 features, see Healthwatch v2.2 Release Notes.

Upgrade to Healthwatch v2.2

The architecture of Healthwatch v2.2 is entirely different from the architecture of Pivotal Healthwatch v1. Because of this, you must install and configure Healthwatch v2.2 as a new tile even if you are upgrading from Pivotal Healthwatch v1. However, if you still rely on metrics from Pivotal Healthwatch v1, you can keep Pivotal Healthwatch v1 installed and use it concurrently with Healthwatch v2.2 while you transition to Healthwatch v2.2.

To upgrade to Healthwatch v2.2:

Review the limitations and risks of using of Healthwatch v2.2. For more information about the limitations of Healthwatch v2.2, see Healthwatch v2.2 Limitations in Healthwatch for VMware Tanzu. For more information about the risks of using Healthwatch v2.2, see Assumed Risks of Using Healthwatch v2.2 in Healthwatch for VMware Tanzu.
Review the configuration options for Healthwatch v2.2 to determine which tiles you must install on your Ops Manager foundations. For more information, see Configuration Options in Healthwatch Architecture.
Install the Healthwatch v2.2 tile and Healthwatch Exporter tiles on the Ops Manager foundations you want to monitor according to the configuration you identified in the previous step, even if you have the Pivotal Healthwatch v1 tile installed already. For more information about installing the Healthwatch v2.2 tile and Healthwatch Exporter tiles, see Installing a Tile Manually or Installing, Configuring, and Deploying a Tile Through an Automated Pipeline.
Configure the Healthwatch component VMs through the Healthwatch v2.2 tile and Healthwatch Exporter tile UIs in the Ops Manager Installation Dashboard and deploy the tiles. For more information about configuring and deploying the tiles, see Configuring Healthwatch, Configuring Healthwatch Exporter for TAS for VMs, and Configuring Healthwatch Exporter for TKGI.
When you no longer need to use Pivotal Healthwatch v1, delete the Pivotal Event Alerts tile from your Ops Manager foundations. Then, delete the Pivotal Healthwatch v1 tile from your Ops Manager foundations.
Important: You must delete the Pivotal Event Alerts tile before you delete the Pivotal Healthwatch v1 tile. If you delete the Pivotal Healthwatch v1 tile first, an error prevents you from deleting the Pivotal Event Alerts tile, and you must re-add the Pivotal Healthwatch v1 tile to delete the Pivotal Event Alerts tile.
For more information about deleting tiles, see the Ops Manager documentation.