Application observability via container build-time injection
Inject OneAgent code modules into a container during its build process.
This method of application instrumentation has limitations in linking Kubernetes workloads with monitored containers/processes. To achieve proper relationships and linking, consider using automatic application-only injection.
Review the list of supported applications and versions.
~325 MB for glibc
~290 MB for musl
~650 MB for glibc and musl combined
For ARM architecture, ensure
To integrate OneAgent into the application image, follow the steps below.
You need to manually update OneAgent by rebuilding the container image every time a new version of a code module is needed.
To uninstall OneAgent from application-only monitoring