-
Notifications
You must be signed in to change notification settings - Fork 404
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] Node.js library HTTP2 support in core Node HTTP2 #2754
Comments
newrelic-node-agent-team
moved this from To do: Features prioritized for this sprint
to Triage Needed: Unprioritized Features
in Node.js Engineering Board
Nov 19, 2024
Check this sheet prepared by Java agent team for reference and need similar doc for Node.js |
kmudduluru
moved this from Triage Needed: Unprioritized Features
to Prioritized
in Node.js Engineering Board
Dec 9, 2024
Understand how java agent team supported this. |
kmudduluru
changed the title
[spike] Node.js library HTTP2 support
[spike] Node.js library HTTP2/HTTP3 support
Jan 24, 2025
kmudduluru
changed the title
[spike] Node.js library HTTP2/HTTP3 support
[spike] Node.js library HTTP2 support
Jan 24, 2025
kmudduluru
changed the title
[spike] Node.js library HTTP2 support
[spike] Node.js library HTTP2 support in core Node HTTP2
Jan 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ticket is to do a spike on what it takes to support HTTP2 in core Node. could be a long running transaction similar to what we did in GRPC. Describe the possible approach with pros and cons and share the findings with the team.
Description
Overall intent is to ensure the Node Agent HTTP instrumentation works properly with the HTTP 2 protocol.
The text was updated successfully, but these errors were encountered: