Broadcom WatchTower Platform Observability

Name: Broadcom WatchTower Platform Observability
Brand: Broadcom
Rating: 4.2 (11 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)

Broadcom WatchTower Platform Observability screenshot

01Competitive Landscape

Narrative analysis

Where WatchTower is differentiated: - The primary differentiation is enabling mainframe telemetry to be integrated into mainstream observability platforms using OpenTelemetry streams, rather than directly competing as a full replacement for those platforms. Where competitors can excel: - Mainstream observability vendors generally provide broader out-of-the-box coverage for cloud-native stacks, larger public review bodies, and more extensive community documentation and how-to content. How customers may choose: - When the objective is end-to-end hybrid tracing that includes mainframe hops, WatchTower’s z/IRIS approach is relevant. - When the objective is cloud-native observability with a self-serve procurement model, mainstream platforms or open-source stacks may be more suitable initially, with mainframe integration considered separately.

	Broadcom WatchTower Platform Observability	Dynatrace	Splunk Observability Cloud
Starting Price	Not clearly published (enterprise licensing typically quoted by vendor)	Published pricing information available from the vendor; often varies by module/consumption and may require a quote or estimator	Published pricing information available from the vendor; final cost depends on scope and telemetry volume
Best For	IBM Z environments needing a mainframe-to-enterprise observability bridge (OpenTelemetry)	Large enterprises seeking automation/AI-driven observability and full-stack coverage	Organizations invested in the Splunk ecosystem seeking unified metrics and traces
Key Strength	Mainframe-native context and OpenTelemetry streaming designed to make mainframe telemetry consumable by enterprise observability platforms	Automation capabilities and enterprise maturity; large support ecosystem	Strong integration within the Splunk ecosystem and operational workflows
Key Weakness	Limited public footprint of WatchTower-specific third-party reviews; setup complexity; limited publicly available WatchTower-specific security documentation	Can be complex to deploy at scale and may have licensing complexity	Can become costly at high telemetry volumes; pricing depends heavily on telemetry retention and ingestion policies

01Competitive Landscape

Narrative analysis

Where WatchTower is differentiated:

The primary differentiation is enabling mainframe telemetry to be integrated into mainstream observability platforms using OpenTelemetry streams, rather than directly competing as a full replacement for those platforms.

Where competitors can excel:

Mainstream observability vendors generally provide broader out-of-the-box coverage for cloud-native stacks, larger public review bodies, and more extensive community documentation and how-to content.

How customers may choose:

When the objective is end-to-end hybrid tracing that includes mainframe hops, WatchTower’s z/IRIS approach is relevant.
When the objective is cloud-native observability with a self-serve procurement model, mainstream platforms or open-source stacks may be more suitable initially, with mainframe integration considered separately.

	Broadcom WatchTower Platform Observability	Dynatrace	Splunk Observability Cloud
Starting Price	Not clearly published (enterprise licensing typically quoted by vendor)	Published pricing information available from the vendor; often varies by module/consumption and may require a quote or estimator	Published pricing information available from the vendor; final cost depends on scope and telemetry volume
Best For	IBM Z environments needing a mainframe-to-enterprise observability bridge (OpenTelemetry)	Large enterprises seeking automation/AI-driven observability and full-stack coverage	Organizations invested in the Splunk ecosystem seeking unified metrics and traces
Key Strength	Mainframe-native context and OpenTelemetry streaming designed to make mainframe telemetry consumable by enterprise observability platforms	Automation capabilities and enterprise maturity; large support ecosystem	Strong integration within the Splunk ecosystem and operational workflows
Key Weakness	Limited public footprint of WatchTower-specific third-party reviews; setup complexity; limited publicly available WatchTower-specific security documentation	Can be complex to deploy at scale and may have licensing complexity	Can become costly at high telemetry volumes; pricing depends heavily on telemetry retention and ingestion policies