You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using eBPF(for go and python) and auto-instrumentation (for java) methods for enabling profiling using alloy to avoid code changes/modificatons and interruptions at application side.
Additionally, we also want to enable profiling on NodeJS applications and it not possible through eBPF or auto-instrumentation and need to go with SDK based profiling as per documentation.
So, request you to please provide suppport for the same.
Use case
As we are already using eBPF and auto-instrumentation methods for profiling go, python and java applications to avoid code changes/modificatons and interruptions at application side, so need to have similar support for NodeJS profiling since it's not feasible/recommended to keep multiple approches and disturb the existing setup.
The text was updated successfully, but these errors were encountered:
Request
We are using eBPF(for go and python) and auto-instrumentation (for java) methods for enabling profiling using alloy to avoid code changes/modificatons and interruptions at application side.
Additionally, we also want to enable profiling on NodeJS applications and it not possible through eBPF or auto-instrumentation and need to go with SDK based profiling as per documentation.
So, request you to please provide suppport for the same.
Use case
As we are already using eBPF and auto-instrumentation methods for profiling go, python and java applications to avoid code changes/modificatons and interruptions at application side, so need to have similar support for NodeJS profiling since it's not feasible/recommended to keep multiple approches and disturb the existing setup.
The text was updated successfully, but these errors were encountered: