IBM Z Log and Data Analytics

Name: IBM Z Log and Data Analytics
Brand: IBM

IBM Z Operational Log and Data Analytics is a mainframe-focused operational analytics solution that streams, filters, transforms, and analyzes IBM Z operational data in near real time and routes Z-aware content to external analytics platforms such as Splunk and Elastic.

Est 1911|Valuation $213.9B|Raised $85.3B

LinkedIn 19.8M|Website|Web traffic 18.9M|FTEs 287,000|HQ Armonk, NY

MarketsData Integration (ETL/ELT)Security Information and Event Management (SIEM)Infrastructure Monitoring Observability Platform

01Competitive Landscape

Narrative analysis

- Situations where IZLDA is appropriate: When an organization already operates a destination analytics platform such as Splunk or Elastic, IZLDA can provide Z-aware content and filtering designed to prepare mainframe operational data for those platforms and to reduce unnecessary downstream ingestion. - Situations where alternatives may be preferable: - Organizations seeking a single vendor-managed APM and observability suite with strong automation and topology features may evaluate Dynatrace or Datadog. - Organizations that require transparent unit pricing for budgeting may find Elastic serverless or other vendors with published rate cards easier to model. - If Z-specific curated dashboards are not required, lightweight pipelines into Kafka or OpenTelemetry collectors combined with custom tooling may suffice, though this approach shifts development and operational burden onto the customer.

	IBM Z Operational Log and Data Analytics (IZLDA)	Splunk Platform	Elastic Observability	Dynatrace
Starting Price	Not publicly published; enterprise quoting typical	Sales-led pricing for enterprise features; multiple licensing models	Serverless observability pricing published with unit-based ingest/retention; requires volume estimates	Public pricing and rate card available for many units (host-hours, ingest, etc.)
Most suitable for	Organizations that require Z-aware data streaming and curated Z content routed to existing analytics platforms	Organizations standardizing around Splunk for log search, correlation, and SIEM use cases	Teams seeking search-centric log analytics with transparent serverless pricing models	Organizations seeking an integrated APM, infrastructure, and log solution with published pricing units and mainframe monitoring capabilities
Key strengths	Z-specific content and a CDPz-based pipeline that supports multiple destinations and filtering	Powerful search and correlation capabilities with broad enterprise adoption	Transparent serverless ingest/retention pricing and strong search and dashboarding capabilities	Automated observability features, topology detection, and published pricing metrics for mainframe monitoring
Key weaknesses	Limited independent review coverage for the specific product; realized value depends on destination platform and observability practice maturity	Cost forecasting and pricing complexity reported by some users	Cost modeling still required; feature and hosting variations across tiers may affect comparisons	Enterprise sales processes and minimum commitments can be a procurement consideration

01Competitive Landscape

Narrative analysis

Situations where IZLDA is appropriate: When an organization already operates a destination analytics platform such as Splunk or Elastic, IZLDA can provide Z-aware content and filtering designed to prepare mainframe operational data for those platforms and to reduce unnecessary downstream ingestion.
Situations where alternatives may be preferable:
- Organizations seeking a single vendor-managed APM and observability suite with strong automation and topology features may evaluate Dynatrace or Datadog.
- Organizations that require transparent unit pricing for budgeting may find Elastic serverless or other vendors with published rate cards easier to model.
- If Z-specific curated dashboards are not required, lightweight pipelines into Kafka or OpenTelemetry collectors combined with custom tooling may suffice, though this approach shifts development and operational burden onto the customer.

	IBM Z Operational Log and Data Analytics (IZLDA)	Splunk Platform	Elastic Observability	Dynatrace
Starting Price	Not publicly published; enterprise quoting typical	Sales-led pricing for enterprise features; multiple licensing models	Serverless observability pricing published with unit-based ingest/retention; requires volume estimates	Public pricing and rate card available for many units (host-hours, ingest, etc.)
Most suitable for	Organizations that require Z-aware data streaming and curated Z content routed to existing analytics platforms	Organizations standardizing around Splunk for log search, correlation, and SIEM use cases	Teams seeking search-centric log analytics with transparent serverless pricing models	Organizations seeking an integrated APM, infrastructure, and log solution with published pricing units and mainframe monitoring capabilities
Key strengths	Z-specific content and a CDPz-based pipeline that supports multiple destinations and filtering	Powerful search and correlation capabilities with broad enterprise adoption	Transparent serverless ingest/retention pricing and strong search and dashboarding capabilities	Automated observability features, topology detection, and published pricing metrics for mainframe monitoring
Key weaknesses	Limited independent review coverage for the specific product; realized value depends on destination platform and observability practice maturity	Cost forecasting and pricing complexity reported by some users	Cost modeling still required; feature and hosting variations across tiers may affect comparisons	Enterprise sales processes and minimum commitments can be a procurement consideration