Users may observe that Diego memory and disk reporting metrics are missing or blank within the Tanzu Hub dashboard for specific foundations.
hub-tas-collector logs may show successful connectivity but a lack of incoming metric payloads for Diego cells.This issue is caused by a regression in the OpenTelemetry (OTel) component integrated within FoundationCore 3.3.0. The regression prevents the collector from correctly processing and forwarding Diego-specific resource metrics (memory and disk) to the Tanzu Hub telemetry pipeline.
There is no configuration-based workaround for the OTel regression in version 3.3.0. An upgrade to a patched version of FoundationCore is required to resolve the defect.
For diagnostic purposes, you can confirm the metrics gap by inspecting the collector logs: bosh -d hub-tas-collector-<deployment_id> logs
Subscribe to this article for updates so you can be informed when the fix is published in a new release.