Pivotal Healthwatch v1.8 Release Notes
- Releases
-
Known Issues
- Push Monitoring Components Errand Fails on Azure
- Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later
- Disk Slowly Fills When Using vSAN with Healthwatch Leads
- BOSH Health Check Fails After Re-Installating Healthwatch
- Indicator Protocol Beta Dashboard Displays Error Due to Log Cache
- Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags
- Metrics Troubleshooting Errand Fails When External Databases Are Configured
Page last updated:
This topic contains release notes for Pivotal Healthwatch v1.8.
Releases
v1.8.8
Release Date: December 22, 2021
- [Security Fix] Apache Log4J dependencies are updated to v2.17.0 to address a critical CVE. For more information, see CVE 2021-45105 on the CVE website.
v1.8.7
Release Date: December 16, 2021
- [Security Fix] Apache Log4J dependencies are updated to v2.16.0 to address a critical CVE. For more information, see CVE 2021-44228 on the CVE website.
v1.8.6
Release Date: December 10, 2021
- [Security Fix] Apache Log4J dependencies are updated to v2.15.0 to address a critical CVE. For more information, see CVE 2021-44228 on the CVE website.
v1.8.5
Release Date: September 2, 2021
[Feature] Pivotal Healthwatch supports VMware Tanzu Application Service for VMs (TAS for VMs) v2.11.
[Feature Improvement] The
health-check-type
used for the Metrics Troubleshooting errand is changed tohttp
to increase reliability.[Known Issue] The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Known Issue] In Pivotal Application Service (PAS) Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, Loggregator fails to emit the
loggregator.syslog_agent.ingress.all_drains
andloggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail. For more information, see Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later below.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
[Known Issue] The Metrics Troubleshooting errand fails when TAS for VMs uses external databases. For more information, see Metrics Troubleshooting Errand Fails When External Databases Are Configured below.
v1.8.4
Release Date: February 5, 2021
[Feature Improvement] Upgrades Java version for security fix.
[Known Issue] The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Known Issue] In PAS Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, Loggregator fails to emit the
loggregator.syslog_agent.ingress.all_drains
andloggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail. For more information, see Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later below.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
[Known Issue] The Metrics Troubleshooting errand fails when TAS for VMs uses external databases. For more information, see Metrics Troubleshooting Errand Fails When External Databases Are Configured below.
v1.8.3
Release Date: January 14, 2021
[Feature Improvement] Upgrades PXC to v0.31.0.
[Feature Improvement] Removes the port check from the
healthwatch-forwarder
monit file. Due to long JVM startup times, this check can cause the monit script to restart, ultimately causinghealthwatch-forwarder
to fail to start until the JVM starts quickly enough.[Bug Fix]
healthwatch-forwarder
quotes foundation names to ensure the foundation name does not get truncated.[Known Issue] The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Known Issue] In PAS Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, Loggregator fails to emit the
loggregator.syslog_agent.ingress.all_drains
andloggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail. For more information, see Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later below.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
[Known Issue] The Metrics Troubleshooting errand fails when TAS for VMs uses external databases. For more information, see Metrics Troubleshooting Errand Fails When External Databases Are Configured below.
v1.8.2
Release Date: September 29, 2020
[Feature] Adds support for TAS for VMs v2.10.
[Bug Fix] Adds a workaround for the Azure bug where running the Push Monitoring Components errand fails on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Bug Fix] Cleans up
cf-health-check
temporary files periodically to limit disk usage.[Known Issue] The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Known Issue] In PAS Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, Loggregator fails to emit the
loggregator.syslog_agent.ingress.all_drains
andloggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail. For more information, see Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later below.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
[Known Issue] The Metrics Troubleshooting errand fails when TAS for VMs uses external databases. For more information, see Metrics Troubleshooting Errand Fails When External Databases Are Configured below.
v1.8.1
Release Date: March 11, 2020
Breaking Change: The delete-space
errand
is renamed to cleanup
. If you use automation scripts that reference this errand,
such as automated pipelines, update the errand name from delete-space
to cleanup
.
[Bug Fix] Fixes issue where super metrics were lost when ingestor instances were overloaded by router latency metrics.
[Known Issue] The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure. For more information, see Push Monitoring Components Errand Fails on Azure below.
[Known Issue] In PAS Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, Loggregator fails to emit the
loggregator.syslog_agent.ingress.all_drains
andloggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail. For more information, see Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later below.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
[Known Issue] The Metrics Troubleshooting errand fails when TAS for VMs uses external databases. For more information, see Metrics Troubleshooting Errand Fails When External Databases Are Configured below.
v1.8.0
Release Date: December 18, 2019
[Feature] Ingresses metrics from the Reverse Log Proxy (RLP) in Loggregator Firehose v2 instead of Traffic Controllers in Loggregator Firehose v1. The RLP has a more configurable API and a longer support window. For more information, see the Loggregator RLP documentation on GitHub.
[Feature] Adds Syslog and Forwarder Agents to Pivotal Healthwatch VMs, which emit syslog directly from the VM rather than through the Firehose.
[Feature Improvement] Removes
Adapter Loss Rate
andCF Syslog Drain Binding Count
from Healthwatch.[Feature Improvement] Renames
log_cache.cache_period
tolog_cache.log_cache_cache_period
to align with Open Metrics naming conventions.[Known Issue] The vSAN object count increases on vSphere v6.5.1 and earlier. For more information, see Disk Slowly Fills When Using vSAN with Healthwatch Leads below.
[Known Issue] If Healthwatch is uninstalled and re-installed while the
bosh-health-check
app is running, thebosh-health-check
app fails to deploy and reports an error in the Healthwatch UI. For more information, see BOSH Health Check Fails After Re-Installating Healthwatch below.[Known Issue] The Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
For more information, see Indicator Protocol Beta Dashboard Displays Error Due to Log Cache below.[Known Issue] In Pivotal Isolation Segment v2.8, Healthwatch cannot accurately measure Diego Cell capacity in compute isolation segments without placement tags. For more information, see Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags below.
Known Issues
Pivotal Healthwatch v1.8 includes the following known issues:
Push Monitoring Components Errand Fails on Azure
The Push Monitoring Components errand pushes the Healthwatch components in parallel, which can cause the errand to fail on Azure.
To work around this issue:
In the Healthwatch tile, select Healthwatch Component Config.
Disable the Push Healthwatch Applications in Parallel checkbox. Disabling this checkbox changes the Push Monitoring Components errand’s deployment strategy from parallel to sequential.
Click Save.
Re-deploy Healthwatch.
Smoke Tests Errand Fails When Installed with PAS Small Footprint v2.8 and Later
In PAS Small Footprint v2.8 and TAS for VMs Small Footprint v2.9 and later, a bug causes Loggregator
to fail to emit the loggregator.syslog_agent.ingress.all_drains
and loggregator.syslog_agent.dropped.egress
metrics. This causes the Smoke Tests errand in Healthwatch to fail.
To work around this issue:
In the Healthwatch tile, select Errands.
Set the Smoke Tests errand to Off.
Click Save.
Re-deploy Healthwatch.
Disk Slowly Fills When Using vSAN with Healthwatch Leads
The vSAN object count increases on vSphere v6.5.1 and earlier.
Healthwatch deploys the bosh-health-check
app, which deploys and deletes a VM every 10 minutes.
vSphere v6.5.1 and earlier leave a namespace or folder and subfolders when the VM is deleted.
The orphaned folders cause the vSAN object count to increase. This is a known issue for vSAN.
For more information, see Deleted VMs leave components behind
in GitHub.
To address the issue, update vSphere to v6.5.2 or later. Otherwise, stop the bosh-health-check
app to slow down the increase in vSAN object count.
BOSH Health Check Fails After Re-Installating Healthwatch
If Healthwatch is uninstalled and re-installed while the bosh-health-check
app is running,
the bosh-health-check
app fails to deploy and reports an error in the Healthwatch UI.
To address this issue:
Manually delete the
bosh-health-check
deployment.Restart the
bosh-health-check
app.
Indicator Protocol Beta Dashboard Displays Error Due to Log Cache
Occasionally, the Indicator Protocol Beta dashboard charts fail to load with the error
"Error fetching graph data."
These charts are populated using Log Cache, a component of Loggregator. Log Cache fails periodically when it times out while attempting to process the data.
No corrective action is required.
Healthwatch Reports False Capacity Metrics for Isolation Segments Without Placement Tags
In Pivotal Isolation Segment v2.8, you can deploy compute isolation segments without placement tags. This allows you to deploy a separate group of Diego Cells without isolating the Diego Cell capacity from other apps. For more information about this feature, see Compute and Networking Isolation in Pivotal Isolation Segment v2.8 Release Notes.
If you deploy compute isolation segments without placement tags, Healthwatch cannot accurately measure Diego Cell capacity. Capacity charts, calculated capacity metrics such as free chunks, and capacity alerts may incorrectly report a lower capacity than is available for apps.
Metrics Troubleshooting Errand Fails When External Databases Are Configured
The Metrics Troubleshooting errand expects certain MySQL metrics to be present. If you configured TAS for VMs to use external databases, the errand fails.
To work around this issue:
In the Healthwatch tile, select Errands.
Set the Metrics Troubleshooting errand to Off.
Click Save.
Re-deploy Healthwatch.