As I stated in my other reply in this thread, DataPower does have a built-in OpenTelemetry exporter and sampler that you can activate on the appliances.
One problem we've discovered with it though is that it doesn't seem to propagate context if it receives a request that already has OTEL trace data in it.
A lot of our API requests go through two DataPowers. An external one that sits in our DMZ and an internal one that does some transformations. We've insured that the traceparent and tracestate headers are getting propogated through them and, when we see the OTEL traces from the internal appliance, we see the traceparent header with the correct trace id from the external appliance where the request originally came in, but for some reason DataPower still creates a whole new trace id on the internal one. It makes no sense. We put a support case in with DataPower. We'll see how it goes.
