Skip to content

Conversation

@janan07
Copy link
Collaborator

@janan07 janan07 commented Jan 20, 2026

Describe your pull request here: This is the working branch for dev use that targets the OTel feature branch

List the file(s) included in this PR:

After creating the PR, follow the instructions in the comments.

Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions
Copy link

😺 Thank you for creating this PR! To publish your content to Zowe Docs, follow these required steps.

  • Add the label review: doc.
  • Identify your content topic with a label. (Examples: area: apiml, area: cli, area: install and config, etc.)
  • Specify the major Zowe release(s) for your content. (Examples: release: V1, release: V2, release: V3)
    • If adding content that needs to be removed from V3 documentation, add the V3 N/A tag.
  • Select the master branch if your PR updates content that is on the live site. Select docs-staging if your PR updates content for a future release.
  • Notify the Doc Squad about this PR. If you don't know whom should review your content, message the #zowe-doc Slack channel. If you know which Doc Squad writer should approve your content, add that person as a reviewer.

Need help? Contact the Doc Squad in the #zowe-doc Slack channel.

@github-actions
Copy link

📁 The PR description is missing the file name(s) for the updated content. List all the files included in this PR so this information displays in our Zowe Docs GitHub Slack channel.

If you have addressed this issue already, refresh this page in your browser to remove this comment.

@janan07 janan07 requested a review from richard-salac January 20, 2026 10:26
@janan07 janan07 added area: apiml This issue is related to Zowe API Mediation Layer release: V3 Zowe V3 content review: sme Needs review by an SME labels Jan 20, 2026
@github-actions
Copy link

github-actions bot commented Jan 20, 2026

@github-actions github-actions bot temporarily deployed to pull request January 20, 2026 10:32 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 20, 2026 10:47 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 20, 2026 16:05 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 21, 2026 10:52 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 21, 2026 13:20 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 22, 2026 09:53 Inactive
Copy link
Member

@balhar-jakub balhar-jakub left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From the skeleton point of view, these are the only changes that would make the usage of the skeleton easier.

Let me know once the general explanation is available and I will review this part.

Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 22, 2026 10:56 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 22, 2026 11:12 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 22, 2026 13:46 Inactive
@github-actions github-actions bot temporarily deployed to pull request January 27, 2026 14:31 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 27, 2026 15:22 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 27, 2026 15:54 Inactive
Signed-off-by: Andrew Jandacek <[email protected]>
Signed-off-by: Andrew Jandacek <[email protected]>
@github-actions github-actions bot temporarily deployed to pull request January 27, 2026 16:22 Inactive
@janan07 janan07 changed the base branch from docs-staging to janan07/otel-feature-branch January 28, 2026 10:50
@janan07 janan07 changed the title create skeleton of OTel OTel working branch targeting OTel feature branch Jan 28, 2026
Groups services into logical sets. Use this property value to distinguish between different installations, such as sysplex-a vs. sysplex-b, or north-datacenter vs. south-datacenter. `service.name` is expected to be unique within the same `namespace`.

* **service.instance.id** (The Unique Instance)
Identifies the specific running process or Address Space. Must be unique for each instance of `service.name` and `service.namespace` pair. On z/OS, this property is typically mapped to the Job Name or a unique UUID.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not true with jobname. Instance id must be globally unique. All instances on different lpars may have the same job name.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this better?

  • service.instance.id (The Unique Instance)
    Identifies a specific running process or Address Space. This value must be globally unique for every instance. As multiple z/OS systems can run identical Job Names, ensure that you combine the Job Name with a unique identifier (such as the LPAR name or a UUID) to ensure the instance can be isolated during troubleshooting.

resource:
attributes:
service.name: "zowe-apiml"
service.namespace: "production-plex"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest we put only examples of complete configuration instead of partial ones to specific attribute groups. For instance, here I would expect the 'production' to be set as deployment attribute

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you suggesting then that we remove all configuration examples in this article or replace them with the complete configuration? If the latter, can you provide me with the complete configuration?

* **resource.attributes**
A collection of key-value pairs used to identify the telemetry source. See the following sub-properties of `resource.attributes`:

* **service.name**
Copy link
Contributor

@richard-salac richard-salac Jan 28, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here we duplicate the explanation of service attributes that we have in a separate md file just for them. Similarly for the deployment. It will be difficult to keep them in sync over time.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you think it's sufficient, I can link to the specific attribute article for these three resources. It just seems that if we have an article for enablement, the user should have an easy reference to what parms are being configured...

@github-actions github-actions bot temporarily deployed to pull request January 28, 2026 14:46 Inactive
Copy link
Collaborator

@iansergeant42 iansergeant42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking pretty good. Just a few things to address.

@@ -0,0 +1,96 @@
# Configure OpenTelemetry Service Attributes

Services are identified via the service.name, service.namespace, and service.instance.id properties. Together, these attributes create a unique identity for API ML instances across your enterprise.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

service.name, service.namespace, and service.instance.id? Trying to be consistent...


## z/OS Attribute Reference

The following attributes are captured during system discovery to describe the mainframe environment:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of things:

  1. Can we describe what 'system discovery' means here? What actually populates the attributes? Our junior sys prog won't understand it.
  2. Given Richard's statement on process.pid not being configured by system discovery, does this move to another section?

Comment on lines +18 to +20
* **exporter.otlp.protocol**
The protocol is either `grpc` or `http/protobuf`.
**Default:** `grcp`
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To note here that if we do reinstate, we have a typo with grpc and grcp mentioned.

exporter:
otlp:
endpoint: "http://otel-collector.your.domain:4317"
protocol: "grpc"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be removed as per Richard above

@@ -0,0 +1,22 @@
# Using Your API ML OpenTelemetry Metrics

## Examples of Useability of Telemetry data in API ML
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo. Usability.

@github-actions github-actions bot temporarily deployed to pull request January 29, 2026 10:28 Inactive
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: apiml This issue is related to Zowe API Mediation Layer release: V3 Zowe V3 content review: sme Needs review by an SME

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants