Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spike: Update HttpClient usage to better support DNS changes on .NET/.NET Core #1845

Open
nrcventura opened this issue Aug 10, 2023 · 1 comment

Comments

@nrcventura
Copy link
Member

Describe the story, please be clear on scope of the story.

The dotnet agent's current usage of HttpClient for sending data to New Relic mostly follows MIcrosoft's guidance (this analysis is documented in an internal doc). The one thing that was discovered to be missing is setting the PooledConnectionLifetime to an appropriate value (this value is TBD). The agent is already using a single instance of HttpClient.

Acceptance Criteria

  1. The agent uses a single instance of HttpClient to send data to New Relic.
  2. The agent configures an appropriate value for the PooledConnectionLifetime setting.
  3. These changes apply to .net/.net core, and do not apply to .net framework.

Dependencies

N/A

Estimates

t-shirt size: S

@workato-integration
Copy link

@workato-integration workato-integration bot changed the title Update HttpClient usage to better support DNS changes on .NET/.NET Core Spike: Update HttpClient usage to better support DNS changes on .NET/.NET Core Oct 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant