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] Node.js library HTTP2 support #2754

Open
kmudduluru opened this issue Nov 19, 2024 · 2 comments
Open

[spike] Node.js library HTTP2 support #2754

kmudduluru opened this issue Nov 19, 2024 · 2 comments

Comments

@kmudduluru
Copy link
Contributor

kmudduluru commented Nov 19, 2024

Description

Overall intent is to ensure the Node Agent HTTP instrumentation works properly with the HTTP 2 protocol.

As part of this research spike:

[ ] Catalog all the instrumentation related to libraries/frameworks that use the HTTP protocol. This will represent the full population of instrumentation that will need further evaluation
[ ] Identify an appropriate testing strategy to determine whether the identified instrumentation modules work as expected when HTTP 2 is used or not
[ ] When breakage to an instrumentation module is detected, create subsequent GitHub issues to track that work as needed

Acceptance Criteria

When this spike is completed, we should have a full listing of which agent instrumentation modules support the HTTP protocol and whether or not those instrumentation modules work properly with HTTP 2 or not.
Design Consideration/Limitations

Some instrumentation modules may be supporting legacy HTTP libraries/framework versions that don't support HTTP 2. Where that occurs, it should be noted in the catalog in some way
If there's a synergistic benefit in considering the HTTP 3 protocol at the same time, that can be done. However, if it otherwise increases the complexity/effort, this scope should be limited to HTTP 2

@kmudduluru kmudduluru converted this from a draft issue Nov 19, 2024
@workato-integration
Copy link

@newrelic-node-agent-team 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
@kmudduluru
Copy link
Contributor Author

@kmudduluru kmudduluru moved this from Triage Needed: Unprioritized Features to Prioritized in Node.js Engineering Board Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Prioritized
Development

No branches or pull requests

1 participant