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.

Sign up for GitHub

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

Jump to bottom

Connection and read timeouts are no longer mapped for NewRelic #21578

Closed
snicoll opened this issue May 26, 2020 · 1 comment
Closed

Connection and read timeouts are no longer mapped for NewRelic #21578

snicoll opened this issue May 26, 2020 · 1 comment
Assignees
@snicoll
Labels
type: regression A regression from a previous release
Milestone
2.3.1

Comments

@snicoll
Copy link
Member

snicoll commented May 26, 2020

If you use the HTTP client to export metrics to New Relic, the read and connection timeouts are no longer mapped.

See also #21440
@snicoll snicoll added the type: regression A regression from a previous release label May 26, 2020
@snicoll snicoll added this to the 2.3.1 milestone May 26, 2020
@snicoll snicoll self-assigned this May 26, 2020
This was referenced May 26, 2020
Closed
Closed
@snicoll
Copy link
Member Author

snicoll commented May 26, 2020

Closed by 069c31a

@snicoll snicoll closed this as completed May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@snicoll snicoll

Labels
type: regression A regression from a previous release
Projects
None yet
Milestone
2.3.1
Development

No branches or pull requests
1 participant
@snicoll