Application Instance and Usage Metrics Missing After Upgrade to Telemetry 2.1 or Late
search cancel

Application Instance and Usage Metrics Missing After Upgrade to Telemetry 2.1 or Late

book

Article ID: 427274

calendar_today

Updated On:

Products

VMware Tanzu Platform Core

Issue/Introduction

After upgrading to Telemetry 2.1 or later, platform usage reports show missing or unexpectedly low values for metrics such as:

  • Application Instance (AI) counts

  • Core consumption

  • Usage data reported from Operations Manager

  • Usage data reported from individual tiles (for example, TAS)

In analytics or reporting dashboards, affected foundations appear to have stopped reporting data starting around the time of the Telemetry upgrade, even though:

  • Applications continue to run normally

  • No platform health issues are observed

  • No obvious errors are visible in reporting tools

Environment

Tanzu Telemetry for VMware Tanzu 2.1

Cause

This issue is caused by a configuration change introduced in Telemetry 2.1.

In Telemetry 2.0 and earlier, a single checkbox controlled the collection and reporting of both:

  • CEIP data

  • Operational data

Starting with Telemetry 2.1, these data sets were split into two independent configuration options:

  • CEIP Data

  • Operational Data

To receive complete usage and consumption metrics (including Application Instance counts and core usage), both data sets must be enabled.

If only one of the following is selected:

  • Operational Data without CEIP, or

  • CEIP without Operational Data,

then telemetry data from Operations Manager and/or individual tiles will be partially or completely missing from usage reports.

This commonly occurs during upgrades where the previous Telemetry 2.0 configuration is not fully replicated in Telemetry 2.1+, resulting in silent data loss rather than an explicit error.

Resolution

To restore telemetry reporting to the behavior seen in Telemetry 2.0:

  1. Open the Telemetry tile.

  2. In the Settings tab, go to Telemetry Settings

  3. Locate the Telemetry Programs 

  4. Ensure that both of the following options are selected:

    •  Yes, share product operational and usage data for functions such as billing (Operational Data).

    •  Yes, share product analytics to help improve products and services experiences (CEIP).

  5. Save the configuration.

  6. Apply changes via Operations Manager.

Once both data sets are enabled, telemetry reporting resumes and usage data from Operations Manager and individual tiles becomes visible again in reporting systems.

Note: Telemetry data may not appear immediately after applying changes. Allow sufficient time for the next telemetry collection and reporting cycle.