As a result of recent industry attention towards full-stack observability, there are various application performance monitoring (AMP) tools, runtime application self-protection (RASP) tools, and distributed tracing modules (such as OpenTelemetry (OTel), the Distributed Application Runtime (Dapr), etc.) available for different programming languages which may be injected as instrumentation code into an actual application to support a very detailed trace or log collection for subsequent analysis. Using a no- or low-code construct, the observability instrumentation code and the application code may be dynamically bundled together to create the function that is required to execute the relevant transactions. Techniques are presented herein that support a new dynamic, traffic-aware Composable Function that leverages an inbound traffic request (comprising metadata and various attributes with, for example, the relevant tracing context header, custom Hypertext Transfer Protocol Secure (HTTPS) header, or OTel header with baggage) to identify and determine whether a function bundle should be composed with observability, APM, or RASP tools for the efficient utilization of the resource. Such a dynamically composed function may, in turn, be hosted as one or more containers within a pod or as a serverless function to provide more flexibility across different application and cluster environments.

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.