英文:
How to - enable distributed tracing on our z/OS Connect servers (based on WebSphere liberty Profile and open-liberty)?
问题
我今天写信给你,请求在与API请求方合作时,在COBOL程序(在在线CICS事务范围内)通过zCEE通信存根激活API时,协助启用z/OS Connect和CICS中的分布式跟踪。
我对z/OS、CICS、COBOL开发、REXX、JCL、Java、WAS Liberty和z/OS Connect有很好的了解。然而,我仍然不确定如何在我们的JVM和系统中激活这种“跟踪器”。
在与IBM进行了基本咨询后(打开了一个案例),他们引荐了我们这个资源:https://github.com/WASdev/sample.opentracing.zipkintracer#readme 但根据该资源,我们仍然无法理解能够帮助我们成功完成此任务的A-Z步骤。
如果您能为我提供更多技术支持来帮助我完成这项任务,我将不胜感激。
已安装的产品:
API-M是WSO2 System
ZCEE版本 - 3.0.3
Build Toolkit版本 - 1.2(20200512-1224)
Liberty版本 - WAS FOR Z/OS 19.0.0.12
RELEASE z/OS 02.04.00 LICENSE = zNALC
CICS事务服务器版本 5.6.0
感谢您的时间和考虑,
真诚地,
Alon
在我们的z/OS Connect服务器代码上添加仪器以生成具有<feature>opentracing-1.0</feature>的跟踪数据。
英文:
I am writing to you today to request assistance in enabling distributed tracing in z/OS Connect and CICS while working with API requesters - from COBOL routines (in the scope of online CICS transactions) that activates APIs via the zCEE communication stubs.
I have a good understanding of z/OS, CICS, COBOL development, REXX, JCL, Java, WAS Liberty, and z/OS Connect. However, I am still not sure how to activate these kind of 'tracers' in our JVMs and systems.
after a basic consultation with IBM (opened a case), they referred us to the resource: https://github.com/WASdev/sample.opentracing.zipkintracer#readme but according to that resource we still couldn't understand the A-Z steps that will help us complete this mission successfully..
I would appreciate it if you could provide me with more technical support to help me with this task.
Installed products:
API-M is the WSO2 System<br>
ZCEE version - 3.0.3<br>
Build Toolkit Version - 1.2 (20200512-1224)<br>
Liberty Version - WAS FOR Z/OS 19.0.0.12<br>
RELEASE z/OS 02.04.00 LICENSE = zNALC<br>
CICS Transaction Server Version 5.6.0
Thank you for your time and consideration,
Sincerely,
Alon
Instrument our z/OS Connect server code to generate tracing data with the <feature>opentracing-1.0</feature>
答案1
得分: 2
Here is the translated content:
根据您需要的跟踪/监控信息类型,以下是描述所需配置的文档相关部分的链接。
在我进一步说明之前,请注意:
- 您提到的 z/OS Connect 版本(3.0.3)相当旧,下面链接中讨论的一些监控功能尚未引入。如果可能的话,建议升级到最新版本(3.0.70):-)
- 下面的链接是针对 z/OS Connect OpenAPI 2 服务器的,因为我假设您正在使用这个版本,考虑到您的版本号。还有一个 z/OS Connect OpenAPI 3 服务器(去年引入),以更标准化的方式提供指标和统计信息。更多信息请参见:https://www.ibm.com/docs/en/zos-connect/zos-connect/3.0?topic=zos-connect-monitoring
回到您可以在 z/OS Connect OpenAPI 2 服务器中进行的操作...
对于请求级别的监控,有多种选项基于 z/OS Connect 的拦截器框架。
- SMF 123 记录通过 z/OS Connect 的审计拦截器捕获了有关每个请求的详细信息:https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=interceptors-configuring-audit-interceptor
- 使用来自 Z 基础监控工具(如 Omegamon for JVM)的拦截器实时监控请求:https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/nigel-williams2/2021/01/23/new-features-in-ibm-z-omegamon-for-jvm-v550-fix-pa
- 使用 Z APM Connect 拦截器将数据发送到端到端请求跟踪工具,如 Instana:https://www.ibm.com/docs/en/iooz?topic=components-tracking-zos-connect-enterprise-edition
所有这些选项都在 z/OS Connect 文档的监控页面中讨论或链接到:https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=monitoring
对于内部跟踪和调试,请参阅文档的问题解决部分:https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=resolving-problems
最后,请参阅部署规划指南的第40页和第49-58页,可在此处获取:http://ibm.biz/zcee-deployment-guide,这些内容在概念层面上讨论了上述所有内容,可能有助于理解监控和跟踪的主题。
希望这有所帮助
英文:
Depending on the type of trace/monitoring information you are after, here are a few links to the relevant parts of the documentation that describe the configuration required.
Before I go any further though, a few notes:
- The version of z/OS Connect you said you are using (3.0.3) is quite old and some of the monitoring features discussed in the links below had not yet been introduced. I suggest upgrading to the latest version (3.0.70) if possible
- The links below are for z/OS Connect OpenAPI 2 servers, since I assume that’s what you are using given the version number you are on. There is also a z/OS Connect OpenAPI 3 server (introduced last year) that provides metrics and statistics in a more standardised fashion. More info here: https://www.ibm.com/docs/en/zos-connect/zos-connect/3.0?topic=zos-connect-monitoring
Back to what you can do in the z/OS Connect OpenAPI 2 server...
For request level monitoring there are number options based around z/OS Connect’s interceptor framework.
- SMF 123 records capture details about each request flowing through z/OS Connect via the audit interceptor provided with z/OS Connect https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=interceptors-configuring-audit-interceptor
- Using interceptors from Z based monitoring tools (like Omegamon for JVM) to monitor requests in realtime: https://community.ibm.com/community/user/ibmz-and-linuxone/blogs/nigel-williams2/2021/01/23/new-features-in-ibm-z-omegamon-for-jvm-v550-fix-pa
- Using the Z APM Connect interceptor to send data to end to end request tracking tools like Instana: https://www.ibm.com/docs/en/iooz?topic=components-tracking-zos-connect-enterprise-edition
All of these options are discussed or linked to from the Monitoring page in the z/OS Connect documentation: https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=monitoring
For internal trace and debugging, that’s covered in the problem resolution part of the documentation:
https://www.ibm.com/docs/en/zos-connect/zosconnect/3.0?topic=resolving-problems
Finally pages 40 & 49-58 of the deployment planning guide available here: http://ibm.biz/zcee-deployment-guide discuss all of the above at a conceptual level and may be helpful to understanding the topic of monitoring and trace.
I hope that helps
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库,让每个人都能够通过互相帮助和分享经验来进步。
评论