The components required for tracing the ABL client are ABL client, OpenTelemetry (OTel)
Collector, and Application Performance Monitoring (APM) tool.
The following diagram depicts OTel tracing for the ABL client:
ABL client—Includes any OpenEdge application, with or without its user interface. When
the ABL client is enabled for tracing, it sends trace data to the configured
OTel Collector using the OTLP protocol.
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.
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.