Broadcom Tanzu Observability

Name: Broadcom Tanzu Observability
Brand: Broadcom
Rating: 4.2 (28 reviews)

Leader

Broadcom provides semiconductors and infrastructure software for global organizations’ complex, mission-critical needs

Est 1961|Valuation $1764B

LinkedIn 446K|Website|Web traffic 4.0M|FTEs 33,000|HQ Palo Alto, California, US

MarketsInfrastructure Monitoring Observability Platform Application Performance Monitoring (APM)

Published Oct 9, 2026

01Common complaints

1) If an organization is initiating a new purchase in 2026 and requires a durable, actively developed observability platform: the published EOL date (October 31, 2025) introduces material procurement and operational risk unless an extension or replacement has been announced by the vendor. 2) If an organization requires transparent, self-serve pricing and predictable expansion economics: some competitors publish detailed rate cards, while this product’s pricing is commonly quote-driven. 3) If minimizing vendor/portfolio turbulence is a priority: public feedback indicates that frequent renames and SKU or portal transitions have caused discoverability and supportability issues. 4) If tightly integrated digital experience monitoring (RUM/session replay/synthetics) is a core requirement: other vendors in the market have clearer feature sets in these areas based on public materials and market positioning; the materials retrieved for this review did not confirm parity in these modules.

Deal disqualifiers

Organizations requiring a clear multi-year roadmap and active service availability should treat the published EOL date as a gating issue and seek clarity from the vendor before proceeding.

End-of-Life / availability

The vendor’s support portal states the service will no longer be provided as of October 31, 2025. This is a primary limitation and should prompt migration planning or avoidance for new purchases unless the vendor provides an alternative program.

Branding / product identity drift

Frequent name changes (Wavefront → Tanzu Observability → Aria Operations for Applications) have caused confusion and can hamper documentation discoverability and supportability.

Portal transitions

Vendor documentation indicates that some Tanzu cloud services were migrated to a new console in 2024, which can affect SSO, tenant management, and operational workflows.

Missing public roadmap detail (in retrieved sources)

A current 2026 product roadmap for Tanzu Observability was not located during this review; this is particularly relevant given the published EOL.

02Why they buy

Documented/claimed differentiators

- Scale reporting: Vendor materials report high ingestion capacity (for example, a reported 250 million data points per minute); treat such figures as vendor-reported and validate methodology. - Query/analytics heritage: The product traces its query and analytics lineage to Wavefront Query Language and has documented PromQL translation support intended to assist teams migrating from Prometheus. - Documented security posture: The vendor whitepaper lists ISO 27001/27017/27018 and SOC 2 Type 1 completion at the time of the whitepaper’s publication; purchasers should verify current certifications.

Where competitors have clearer advantages

Datadog: broad integration ecosystem and a mature SaaS user experience as positioned in market materials.
Dynatrace: public rate cards and a combined observability/automation/security focus in vendor materials.

03Field reports

Review platform visibility limitations

Some industry review platforms maintain product-level pages that require login or redirect to market-level pages, which can limit direct access to product-specific quotes and full review text.

G2 reviews (Tanzu platform references)

- G2 hosts reviews under the broader Tanzu listing that include mentions of the observability component. Example: reviewers on the broader Tanzu listing have described complexity in Kubernetes management while noting the granularity of the observability tool. These comments appear to reflect the broader Tanzu platform rather than a single product-specific page. Limitations: The G2 listing in this review is for the broader Tanzu suite and may conflate platform and observability feedback.

Community sentiment (common themes)

Community discussions (for example on public forums) frequently note frustration with branding and name changes, which can affect documentation discoverability and supportability.
Community comments also raise concerns about pricing and SKU complexity; some anecdotal posts describe migrations away from the vendor due to perceived pricing changes and renaming.

Third-party comparison/summary content

- Some comparison pages on third-party sites provide directional summaries indicating strengths or weaknesses compared to competitors, but such pages are frequently editorial in nature and should be treated as directional rather than definitive. Why customers chose it (as suggested by vendor materials and third-party summaries): - Alignment with VMware/Tanzu ecosystem is cited as a purchase rationale for VMware-centric organizations. - The vendor positions the product around high-scale metrics ingestion and analytics/query capabilities. Why customers leave / churn risk indicators: - The published EOL notice implies mandatory migration for remaining customers unless an extension has been announced. - Community feedback about pricing complexity and product renaming has been cited as a factor in some migration decisions.

Vendor case study: migration from a competitor (vendor-curated)

A vendor-hosted case study describes a migration from a competitor to Tanzu Observability and reports a fast migration and strong ingestion performance. This is vendor-selected content; methodology and independent verification (for example, baseline metrics, cost analysis, sampling, and time windows) are not provided in the case study excerpts.

Vendor datasheet customer quotes

- Vendor datasheets include customer quotes and logos (for example, a quoted Workday reference). These items provide evidence of enterprise usage but are vendor-curated and should be corroborated via references or third-party sources when possible. Critical evaluation checklist for purchasers: - Request details on: (1) retention terms, (2) ingestion limits, (3) expected costs at current metric cardinality, (4) migration tooling and timelines if EOL applies, and (5) references from customers that are not vendor-selected.

04Best fit

Best-fit organizations (when the service is available)

Company size: Mid-size to large organizations with multiple engineering teams and platform/SRE functions.
Environment: Kubernetes and microservices, hybrid cloud, and a significant vSphere footprint.
Teams/personas: Platform engineering/SRE leads, development leads needing service-level metrics and alerting, and operations teams requiring cross-domain visibility.

Fit signals (qualification criteria)

Existing VMware/Tanzu footprint and the need for vendor-aligned observability.
Primary requirement for high-scale metrics and advanced querying/analytics.

05The pitch

What the product does (objective value proposition)

Broadcom Tanzu Observability (formerly Wavefront; sometimes referenced as Aria Operations for Applications) is an enterprise observability platform that collects and analyzes operational telemetry—primarily metrics, plus traces/spans, histograms, events, and related signals—to support monitoring, alerting, troubleshooting, and performance optimization across cloud-native and hybrid/multi-cloud environments. Broadcom’s datasheet describes the product as providing observability across multiple telemetry types with a focus on high ingestion and analytics designed for large DevOps/SRE organizations, including dashboards and alerting support. The vendor materials also highlight support for distributed applications and Kubernetes environments.

Target market and positioning

Primary target: Mid-market to large enterprises operating Kubernetes/microservices at scale, especially organizations standardized on VMware/Broadcom Tanzu/vSphere ecosystems.
Positioning summary: Positioned for enterprise customers requiring high-volume telemetry ingestion and query/analytics capabilities, with a query language heritage from Wavefront.

Get a comprehensive analysis of Broadcom Tanzu Observability including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 9, 2026

01Common complaints

If an organization is initiating a new purchase in 2026 and requires a durable, actively developed observability platform: the published EOL date (October 31, 2025) introduces material procurement and operational risk unless an extension or replacement has been announced by the vendor.
If an organization requires transparent, self-serve pricing and predictable expansion economics: some competitors publish detailed rate cards, while this product’s pricing is commonly quote-driven.
If minimizing vendor/portfolio turbulence is a priority: public feedback indicates that frequent renames and SKU or portal transitions have caused discoverability and supportability issues.
If tightly integrated digital experience monitoring (RUM/session replay/synthetics) is a core requirement: other vendors in the market have clearer feature sets in these areas based on public materials and market positioning; the materials retrieved for this review did not confirm parity in these modules.

Deal disqualifiers

Organizations requiring a clear multi-year roadmap and active service availability should treat the published EOL date as a gating issue and seek clarity from the vendor before proceeding.

End-of-Life / availability

The vendor’s support portal states the service will no longer be provided as of October 31, 2025. This is a primary limitation and should prompt migration planning or avoidance for new purchases unless the vendor provides an alternative program.

Branding / product identity drift

Frequent name changes (Wavefront → Tanzu Observability → Aria Operations for Applications) have caused confusion and can hamper documentation discoverability and supportability.

Portal transitions

Vendor documentation indicates that some Tanzu cloud services were migrated to a new console in 2024, which can affect SSO, tenant management, and operational workflows.

Missing public roadmap detail (in retrieved sources)

A current 2026 product roadmap for Tanzu Observability was not located during this review; this is particularly relevant given the published EOL.

02Why they buy

Documented/claimed differentiators

Scale reporting: Vendor materials report high ingestion capacity (for example, a reported 250 million data points per minute); treat such figures as vendor-reported and validate methodology.
Query/analytics heritage: The product traces its query and analytics lineage to Wavefront Query Language and has documented PromQL translation support intended to assist teams migrating from Prometheus.
Documented security posture: The vendor whitepaper lists ISO 27001/27017/27018 and SOC 2 Type 1 completion at the time of the whitepaper’s publication; purchasers should verify current certifications.

Where competitors have clearer advantages

Datadog: broad integration ecosystem and a mature SaaS user experience as positioned in market materials.
Dynatrace: public rate cards and a combined observability/automation/security focus in vendor materials.

03Field reports

Review platform visibility limitations

Some industry review platforms maintain product-level pages that require login or redirect to market-level pages, which can limit direct access to product-specific quotes and full review text.

G2 reviews (Tanzu platform references)

G2 hosts reviews under the broader Tanzu listing that include mentions of the observability component. Example: reviewers on the broader Tanzu listing have described complexity in Kubernetes management while noting the granularity of the observability tool. These comments appear to reflect the broader Tanzu platform rather than a single product-specific page.

Limitations: The G2 listing in this review is for the broader Tanzu suite and may conflate platform and observability feedback.

Community sentiment (common themes)

Community discussions (for example on public forums) frequently note frustration with branding and name changes, which can affect documentation discoverability and supportability.
Community comments also raise concerns about pricing and SKU complexity; some anecdotal posts describe migrations away from the vendor due to perceived pricing changes and renaming.

Third-party comparison/summary content

Some comparison pages on third-party sites provide directional summaries indicating strengths or weaknesses compared to competitors, but such pages are frequently editorial in nature and should be treated as directional rather than definitive.

Why customers chose it (as suggested by vendor materials and third-party summaries):

Alignment with VMware/Tanzu ecosystem is cited as a purchase rationale for VMware-centric organizations.
The vendor positions the product around high-scale metrics ingestion and analytics/query capabilities.

Why customers leave / churn risk indicators:

The published EOL notice implies mandatory migration for remaining customers unless an extension has been announced.
Community feedback about pricing complexity and product renaming has been cited as a factor in some migration decisions.

Vendor case study: migration from a competitor (vendor-curated)

A vendor-hosted case study describes a migration from a competitor to Tanzu Observability and reports a fast migration and strong ingestion performance. This is vendor-selected content; methodology and independent verification (for example, baseline metrics, cost analysis, sampling, and time windows) are not provided in the case study excerpts.

Vendor datasheet customer quotes

Vendor datasheets include customer quotes and logos (for example, a quoted Workday reference). These items provide evidence of enterprise usage but are vendor-curated and should be corroborated via references or third-party sources when possible.

Critical evaluation checklist for purchasers:

Request details on: (1) retention terms, (2) ingestion limits, (3) expected costs at current metric cardinality, (4) migration tooling and timelines if EOL applies, and (5) references from customers that are not vendor-selected.

04Best fit

Best-fit organizations (when the service is available)

Company size: Mid-size to large organizations with multiple engineering teams and platform/SRE functions.
Environment: Kubernetes and microservices, hybrid cloud, and a significant vSphere footprint.
Teams/personas: Platform engineering/SRE leads, development leads needing service-level metrics and alerting, and operations teams requiring cross-domain visibility.

Fit signals (qualification criteria)

Existing VMware/Tanzu footprint and the need for vendor-aligned observability.
Primary requirement for high-scale metrics and advanced querying/analytics.

05The pitch

What the product does (objective value proposition)

Broadcom’s datasheet describes the product as providing observability across multiple telemetry types with a focus on high ingestion and analytics designed for large DevOps/SRE organizations, including dashboards and alerting support. The vendor materials also highlight support for distributed applications and Kubernetes environments.

Target market and positioning

Primary target: Mid-market to large enterprises operating Kubernetes/microservices at scale, especially organizations standardized on VMware/Broadcom Tanzu/vSphere ecosystems.
Positioning summary: Positioned for enterprise customers requiring high-volume telemetry ingestion and query/analytics capabilities, with a query language heritage from Wavefront.

Get a comprehensive analysis of Broadcom Tanzu Observability including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →