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
Currently, we have the ability to enable and disable continuous profiling via an environment variable (DD_PROFILING_ENABLED) or the configuration option (profiling: true) during init(). However, this flag must be set on initialization, while we have some cases where we'd like to turn on profiling after the fact (for example, switch a feature flag on to start collecting CPU samples without restarting the service). Is it possible to enable continuous profiling dynamically, after the tracer has been initialized?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, we have the ability to enable and disable continuous profiling via an environment variable (DD_PROFILING_ENABLED) or the configuration option (
profiling: true) duringinit(). However, this flag must be set on initialization, while we have some cases where we'd like to turn on profiling after the fact (for example, switch a feature flag on to start collecting CPU samples without restarting the service). Is it possible to enable continuous profiling dynamically, after the tracer has been initialized?Beta Was this translation helpful? Give feedback.
All reactions