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
Our instrumentation.* params, such as instrumentation.net_http currently support four possible values: disabled, auto, prepend, and chain.
The auto value (the default) sees the agent attempt to dynamically determine whether method prepending or chaining should be used. After this automated determination has been made and the relevant method(s) have been updated, it would be great to be able to query the agent configuration afterwards and introspect whether "chain" or "prepend" was selected.
Given that the "auto" value serves no purpose post dependency detection time, is the default, and can't be set via a server side configuration change, it might be best to simply convert the "auto" value into either a "prepend" or "chain" value so that querying the config for any given instrumentation will expose the method updating approach that was taken.
The text was updated successfully, but these errors were encountered:
Our
instrumentation.*
params, such asinstrumentation.net_http
currently support four possible values:disabled
,auto
,prepend
, andchain
.The
auto
value (the default) sees the agent attempt to dynamically determine whether method prepending or chaining should be used. After this automated determination has been made and the relevant method(s) have been updated, it would be great to be able to query the agent configuration afterwards and introspect whether "chain" or "prepend" was selected.Given that the "auto" value serves no purpose post dependency detection time, is the default, and can't be set via a server side configuration change, it might be best to simply convert the "auto" value into either a "prepend" or "chain" value so that querying the config for any given instrumentation will expose the method updating approach that was taken.
The text was updated successfully, but these errors were encountered: