DataDog · dd-pub-platform · Oct 30, 2025
diff --git a/watchtower_ziris/CHANGELOG.md b/watchtower_ziris/CHANGELOG.md
@@ -0,0 +1,24 @@
+# CHANGELOG - Broadcom WatchTower z/IRIS
+
+## 1.3.0 / 2025-10-30
+
+_**New Features**_:
+
+* Broadcom SYSVIEW customers can configure z/IRIS to  stream OpenTelemetry (OTel) JVM Garbage Collection metrics for enhanced monitoring and performance analysis. For more details, see [OpenTelemetry JVM Garbage Collection Metrics ](https://techdocs.broadcom.com/us/en/ca-mainframe-software/intelligent-operations/watchtower-platform-suite/1-2/reference/z-iris-telemetry/opentelemetry-metrics/opentelemetry-jvm-garbage-collection-metrics.html#_e440c267-53a0-4566-9bc7-896b5e3d0527_JVMGC).
+
+_**Improvements**_:
+
+*  service name granularity has been enhanced by extracting distinguishing precise service identification.
+
+Unit of Work | Service Name
+------|------
+ z/OS Connect API | REST API Name 
+CICS transaction | CICS Region Name
+
+ Users can customize the service name in the OpenTelemetry Collector. For  For detailed steps to customize the service name , see the [z/IRIS OpenTelemetry Collector Configuration](https://techdocs.broadcom.com/us/en/ca-mainframe-software/intelligent-operations/watchtower-platform-suite/1-2/administrating/administrate-ziris/observability-with-opentelemetry/configure-opentelemetry-contrib-collector.html#configuring_opentelemetry_contrib_collector) page.
+
+* z/IRIS IronTap added OTLP/HTTP support for all signal transmission. The existing gRPC transport protocol remains supported. The configuration option is described in the [Complete z/IRIS IronTap Configuration Tasks](https://techdocs.broadcom.com/us/en/ca-mainframe-software/intelligent-operations/watchtower-platform-suite/1-2/installing/install-z-iris/install-z-iris-irontap/configure-z-iris-irontap.html#concept.dita_configure_irontap_container_CTB) page.
+
+ * A new configurable option is available to set the ERROR status on CICS  spans when exception conditions impact the reliability of transaction. See the CICS Transaction Error Reporting section in the [CICS Spans](https://techdocs.broadcom.com/us/en/ca-mainframe-software/intelligent-operations/watchtower-platform-suite/1-2/reference/z-iris-telemetry/spans/cics-spans.html#cics_spans_err) page for steps to configure the span error status.
+
+* Log correlation has been enhanced. Logs are tagged with the trace context (trace_id and span_id), enabling a direct correlation between logs and spans from the same unit-of-work. If a span was not established the log entry will not contain any trace context.
@@ -0,0 +1,64 @@
+# Broadcom WatchTower z/IRIS
+
+## Overview
+
+Reduce your mean time to restore critical business services and improve service availability and reliability for core business applications with WatchTower's Real-Time OpenTelemetry Streaming capability (referred to as z/IRIS). WatchTower is a Broadcom Mainframe Software Product that provides a comprehensive picture of mainframe health, allowing you to anticipate failures based on past patterns, prevent small issues from becoming outages, and proactively manage your operations.  Each WatchTower capability can be used in silo or integrated with other capabilities to significantly broaden the range of contextual insights. 
+
+Installing this WatchTower z/IRIS integration delivers a quick and easy out of the box experience for observability in Datadog:
+- Monitor your z/OS system and applications using WatchTower's curated and customizable dashboards.
+- Enable alerts on resource contention and application anomalies with WatchTowers recommended mainframe monitors.
+- Continuously improve observability practices with access to all future Datadog resources created by WatchTower z/IRIS.
+
+## Setup
+
+**Prerequisite**
+Verify that WatchTower z/IRIS is installed and running. Refer to the WatchTower z/IRIS Installation documentation on techdocs.broadcom.com for more information about installing z/IRIS in your environment. 
+
+**Complete OpenTelemetry Collector Configuration**
+- Configure the OTLP receiver \
+   WatchTower z/IRIS can export telemetry over HTTP or gRPC. Refer to the  z/IRIS IronTap configuration to verify the appropriate receiver is configured.
+- Add the Transform Processor \
+   Add the prefix "ziris." to all opentelemetry basesd metrics streamed from  z/IRIS.
+```json
+transform/datadog:
+   metric_statements:
+      - context: metric
+        statements:
+          - set(name,concat("ziris.", name")) where starts_with((name, "zos.")
+          - set(name,concat("ziris.", name")) where starts_with((name, "irontap.")
+
+```
+- Verify the Datadog Exporter and Connector are setup correctly\
+   Follow Datadog's documentation to setup the Datadog Exporter and Connector for OpenTelemetry integration. 
+- Starting the OpenTelemetry Collector\
+    Verify that z/IRIS metrics is streaming with the correct prefix to Datadog.
+- Install the out-of-the-box WatchTower z/IRIS Dashboards\
+  All Dashobards can be copied and edited to meet your operational requirements.
+- Install the out-of-the-box WatchTower z/IRIS Monitors\
+   z/IRIS Monitors can be enabled to accelerate mean-time-to-restore.
+
+
+
+## Uninstallation
+
+**Mainframe: z/IRIS Client or zArchitecture Bridge (ZAB)** 
+
+1. Identify if z/IRIS Client or ZAB is used to stream mainframe operational data for z/IRIS.
+2. If the z/IRIS Client is implemented: Stop the z/IRIS Client
+3. If ZAB is implemented: Remove subscriptions specific to the z/IRIS installation
+2. Follow in-house procedures to remove SMP/E or z/OSMF installed software
+
+_Note: ZAB can stream operational data for multiple Broadcom products and care should be taken to remove subscriptions that were unique to z/IRIS processing only. _
+
+**Container: z/IRIS IronTap**
+
+Using the commands applicable to your container engine:
+1. Stop all IronTap containers
+2. Remove all IronTap containers.
+
+## Support
+
+Log onto [support.broadcom.com][1] and create a case for WatchTower z/IRIS
+
+
+[1]: https://support.broadcom.com/