Skip to content

Update Broadcom WatchTower z/IRIS integration #2984

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dd-pub-platform wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Update Broadcom WatchTower z/IRIS integration #2984

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8677931
Update Broadcom WatchTower z/IRIS integration
dd-pub-platform[bot] Apr 27, 2026
d9555fc
Update Broadcom WatchTower z/IRIS integration
dd-pub-platform[bot] May 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions watchtower_ziris/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Verify that WatchTower z/IRIS is installed and running. Refer to the WatchTower

### Installation

1. **Configure the OpenTelemetry Collector**
1. Configure the OpenTelemetry Collector

- Configure the OTLP receiver

Expand Down Expand Up @@ -48,15 +48,15 @@ Verify that WatchTower z/IRIS is installed and running. Refer to the WatchTower
2. [Configure the Datadog Exporter and Connector][3]

Follow Datadog's documentation to add the Datadog exporter to your collector configuration and provide your API key.
Add the processors `transform/datadog` to the z/IRIS pipelines exporting signals to your Datadog tenant.
Add the processor `transform/datadog` to the z/IRIS pipelines exporting signals to your Datadog tenant.

3. Launch the collector and verify in Datadog that the renamed metrics (`ziris.*`) are appearing in the [Metrics Explorer][4] and verify that mainframe traces and spans are streaming.
3. Launch the collector. Verify in Datadog that the renamed metrics (`ziris.*`) are appearing in the [Metrics Explorer][4] and that mainframe traces and spans are streaming.

4. In Datadog, open the WatchTower z/IRIS integration tile and click **Install**.

Dashboards will be cloned into your organization, and the monitors will be available on the [Monitor Templates][5] page.

5. In Datadog, open Log explorer and verify that the z/IRIS custom group facets is available for filtering.
5. In Datadog, open Log Explorer and verify that the z/IRIS custom group facets are available for filtering.



Expand Down
19 changes: 7 additions & 12 deletions watchtower_ziris/assets/dashboards/watchtower_z_iris____z_os_connect_overview.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -116,7 +116,7 @@
"id": 2530142959611229,
"definition": {
"type": "note",
"content": "The percentage z/OS Connect REST API requests that failed. A request is considered failed when the ***http.response.status_code*** is within the range of ***400 to 599***, e.g. 404.\n",
"content": "The percentage z/OS Connect REST API requests that failed. A request is considered failed when the ***http.response.status_code*** is within the range of ***400 to 500***, e.g. 404.\n",
"background_color": "green",
"font_size": "14",
"text_align": "left",
Expand All @@ -137,7 +137,7 @@
"id": 7870388388312153,
"definition": {
"type": "note",
"content": "Triggered monitors relevant to APIs hosted on mainframe. Monitors must have the tag \"mainframe-apis\"configured be included. \n\n",
"content": "Triggered monitors relevant to APIs hosted on mainframe. Monitors must have the tag \"mainframe-apis\" configured be included. \n\n",
"background_color": "green",
"font_size": "14",
"text_align": "left",
Expand Down Expand Up @@ -371,7 +371,7 @@
{
"data_source": "metrics",
"name": "query3",
"query": "sum:zos.connect.http.response.codes{$host, $sysplex.name, $server.name, $service, http.response.status_code:2*} by {service.name}.rollup(sum, 60)",
"query": "sum:ziris.zos.connect.http.response.codes{$host, $sysplex.name, $server.name, $service, http.response.status_code:2*} by {service.name}.rollup(sum, 60)",
"aggregator": "sum"
}
],
Expand Down Expand Up @@ -427,7 +427,6 @@
"title": "Top 5 Error Count by API",
"title_size": "16",
"title_align": "left",
"time": {},
"type": "query_table",
"requests": [
{
Expand Down Expand Up @@ -541,7 +540,6 @@
"value",
"sum"
],
"time": {},
"type": "timeseries",
"requests": [
{
Expand Down Expand Up @@ -683,7 +681,7 @@
{
"data_source": "metrics",
"name": "query2",
"query": "sum:zcon_mainframe_duration{$host,$sysplex.name,$server.name,$service} by {service.name}.rollup(sum, 60).as_count()"
"query": "sum:ziris.zos.connect.timed_out_requests{$host,$sysplex.name,$server.name,$service} by {service.name}.rollup(sum, 60)"
}
],
"response_format": "timeseries",
Expand Down Expand Up @@ -780,7 +778,7 @@
{
"data_source": "metrics",
"name": "query2",
"query": "sum:zos.connect.http.response.codes{$host AND $sysplex.name AND $server.name AND $service AND (NOT http.response.status_code:2*)} by {service.name}.rollup(count, 60)"
"query": "sum:ziris.zos.connect.http.response.codes{$host AND $sysplex.name AND $server.name AND $service AND (NOT http.response.status_code:2*)} by {service.name}.rollup(count, 60)"
}
],
"response_format": "timeseries",
Expand Down Expand Up @@ -828,7 +826,7 @@
"id": 1250514767888197,
"definition": {
"type": "note",
"content": "Average time spent on z/OS per API request, meaning meaning _time-spent-on-zos = time-spent-in-zosconnect-server + time-spent-in-system-of-record_.. This does not included network time to send or receive the request from the client application.",
"content": "Average time spent on z/OS per API request, meaning meaning _time-spent-on-zos = time-spent-in-zosconnect-server + time-spent-in-system-of-record_.. This does not include network time to send or receive the request from the client application.",
"background_color": "blue",
"font_size": "14",
"text_align": "left",
Expand Down Expand Up @@ -860,7 +858,6 @@
"value",
"sum"
],
"time": {},
"type": "timeseries",
"requests": [
{
Expand Down Expand Up @@ -925,7 +922,7 @@
"id": 3616341517164885,
"definition": {
"type": "note",
"content": "Average time spent in the z/OS Connect server per API request.\nThis represents a subset of the tot time spent on z/OS per API request, meaning _time-spent-on-zos = time-spent-in-zosconnect-server + time-spent-in-system-of-record_.",
"content": "Average time spent in the z/OS Connect server per API request.\nThis represents a subset of the total time spent on z/OS per API request, meaning _time-spent-on-zos = time-spent-in-zosconnect-server + time-spent-in-system-of-record_.",
"background_color": "blue",
"font_size": "14",
"text_align": "left",
Expand Down Expand Up @@ -957,7 +954,6 @@
"value",
"sum"
],
"time": {},
"type": "timeseries",
"requests": [
{
Expand Down Expand Up @@ -1058,7 +1054,6 @@
"value",
"sum"
],
"time": {},
"type": "timeseries",
"requests": [
{
Expand Down
Loading
Loading