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

Do not instrument the agent's own HTTP calls #2264

Open
fallwith opened this issue Oct 16, 2023 · 1 comment
Open

Do not instrument the agent's own HTTP calls #2264

fallwith opened this issue Oct 16, 2023 · 1 comment
Labels
3 Story Point Estimate

Comments

@fallwith
Copy link
Contributor

Any HTTP call that the agent makes - especially the ones to cloud provider metadata endpoints at 169.254.169.254 - should not itself be instrumented by the agent.

If there are HTTP calls that make sense to leave instrumented, a dev team consensus should be all that's needed to preserve them as instrumented. If ALL existing instrumented calls are thought to be needed, this issue can be "won't-fixed".
@workato-integration
Copy link

https://new-relic.atlassian.net/browse/NR-170688

@kford-newrelic kford-newrelic added estimate Issue needing estimation jan-mar qtr Possible FY Q4 candidate labels Nov 20, 2023
@kford-newrelic kford-newrelic added 3 Story Point Estimate and removed estimate Issue needing estimation labels Dec 20, 2023
@kford-newrelic kford-newrelic removed the jan-mar qtr Possible FY Q4 candidate label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
3 Story Point Estimate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fallwith @kford-newrelic