Idea Summary
Add Opentelemetry support (particularly tracing) in APEX to allow observability across APEX and cloud native components and languages such as, but not limited to, microservices deployed in Kuberenetes.
Use Case
The use case is the bridging/inclusion of observability from APEX to/from cloud-native (or any non-APEX application/service) microservices, etc. world. An APEX frontend (as an option to the existing JavaScript frontend) will be added to the popular “Simplify Microservices With Oracle Converged Database” workshop: https://apexapps.oracle.com/pls/apex/r/dbpm/livelabs/view-workshop?wid=637
Preferred Solution (Optional)
I have described the use of OpenTelemetry across the company in my “DevOps meets DataOps: Oracle's End-to-End OpenTelemetry Observability Across Apps, Kubernetes, and Database” presentation and there is a video of the same here: https://www.youtube.com/watch?v=eUFt3Pzwj30&t=874s The idea is similar to the new ECID functionality that can be found here: https://docs.oracle.com/en/database/oracle/apex/23.1/htmrn/new-features.html#GUID-25199462-9DEC-4B4C-969C-DE397B172688 except it would be the creation and propagation of an OpenTelemetry tracing id/span.