The components required for tracing both the ABL client and the PAS for OpenEdge agent together are ABL client, PAS for OpenEdge agent (including PAS for OpenEdge session manager), OpenTelemetry (OTel) Collector, and Application Performance Monitoring (APM) tool.

The following diagram depicts OTel tracing for both the ABL client and the PAS for OpenEdge agent. In this diagram, the ABL client and the PAS for OpenEdge agent send their trace data to the same OTel Collector:
Note: You have the option to configure the ABL client and the PAS for OpenEdge agent to send trace data to separate OTel Collectors.
  • ABL client—Includes any OpenEdge application with or without its user interface. When the ABL client is enabled for tracing, it generates trace data. It sends trace data to the OTel Collector and trace context to the PAS for OpenEdge agent.
    Note: An ABL client supports OTel tracing only when it is the 64‑bit client running on a 64‑bit Windows system. The 32‑bit ABL client is not supported in any configuration, including on 64‑bit Windows or 32‑bit Windows.

  • PAS for OpenEdge agent—A process that runs your ABL application in your PAS for OpenEdge instance. When the PAS for OpenEdge agent is enabled for tracing, it receives the trace context from the ABL client through the PAS for OpenEdge session manager. The PAS for OpenEdge agent links its generated trace data with those generated by the ABL client using the trace context. It then sends trace data to the configured OTel Collector using the OTLP protocol.

  • OTel Collector—An application that processes trace data and sends it to the APM tool. When the OTel Collector is configured on a system, it can handle multiple processes that generate trace data on the same system.

  • APM tool—Visualizes trace data, allowing you to analyze what your application is doing and where it is spending time. You can use any APM tool that supports the OTel standards, such as Elastic APM, Dynatrace, or NewRelic.