Describe the story, please be clear on scope of the story.
There are a handful of settings that the agent supports that are retrieved using the ConfigurationManager APIs. Our usage of the ConfigurationManager during agent initialization can sometimes lead to deadlock scenarios when the application being monitored has configured the ConfigurationManager to integrate with APIs that the agent also instruments. In some scenarios it can be difficult to get a memory dump to help with identifying which method(s) are triggering the problem. To make it easier to troubleshoot these types of problems, the agent should provide a configuration option (newrelic.config and environment variable) so that the agent's usage of the ConfigurationManager APIs will be skipped.
In order to use this option, customers will need to ensure that any New Relic agent settings they were defining in web.config, app.config, or appsettings.json are migrated into either an app-local newrelic.config file or application specific environment variable.
Acceptance Criteria
The default value for this setting results in the agent using the ConfigurationManager APIs (the current agent behavior)
Disabling this setting results in the agent not using the ConfigurationManager APIs.
Dependencies
None
Describe Design Consideration/Limitations
This is meant to provide a simpler workaround for scenarios where it is more difficult to determine what to add to the current delayed initialization environment variables.
Additional context
This is meant to assist with situations like #2809.
workato-integration[bot]
commented
1 week ago
Describe the story, please be clear on scope of the story.
There are a handful of settings that the agent supports that are retrieved using the ConfigurationManager APIs. Our usage of the ConfigurationManager during agent initialization can sometimes lead to deadlock scenarios when the application being monitored has configured the ConfigurationManager to integrate with APIs that the agent also instruments. In some scenarios it can be difficult to get a memory dump to help with identifying which method(s) are triggering the problem. To make it easier to troubleshoot these types of problems, the agent should provide a configuration option (newrelic.config and environment variable) so that the agent's usage of the ConfigurationManager APIs will be skipped.
In order to use this option, customers will need to ensure that any New Relic agent settings they were defining in web.config, app.config, or appsettings.json are migrated into either an app-local newrelic.config file or application specific environment variable.
Acceptance Criteria
Dependencies
None
Describe Design Consideration/Limitations
This is meant to provide a simpler workaround for scenarios where it is more difficult to determine what to add to the current delayed initialization environment variables.
Additional context
This is meant to assist with situations like #2809.
Estimates
Initial t-shirt size: Small