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

ApolloServerPluginUsageReporting does not allow to pass http agent #7813

Closed
vany0114 opened this issue Jan 4, 2024 · 2 comments
Closed

ApolloServerPluginUsageReporting does not allow to pass http agent #7813

vany0114 opened this issue Jan 4, 2024 · 2 comments

Comments

@vany0114
Copy link
Contributor

vany0114 commented Jan 4, 2024

Issue Description

Hello,

I'm using Apollo Federation in an Azure environment, specifically deployed as an Azure Function. I've noticed that the ApolloServerPluginUsageReporting is causing a lot of connect ETIMEDOUT as it seems it is exhausting the available Websockets/TCP connections when making this request to: HTTP: POST usage-reporting.api.apollographql.com/api/ingress/traces, I guess most likely because it is not reusing the HTTP contention, so I had to disable the reporting as I could not find a way to pass an HTTP agent to the plunging to keep alive the connection to avoid the issue mentioned above.

Is there a workaround or you guys can please point me to the right direction?

Link to Reproduction

N/A

Reproduction Steps

Versions used:

"@apollo/gateway": "^2.5.1",
"@apollo/server": "^4.9.0",
"@apollo/server-plugin-landing-page-graphql-playground": "^4.0.1",
"@apollo/server-plugin-response-cache": "^4.1.3",
"@apollo/subgraph": "^2.5.1",
@glasser
Copy link
Member

glasser commented Jan 4, 2024

Duplicate of #7811

@glasser glasser marked this as a duplicate of #7811 Jan 4, 2024
@glasser glasser closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Copy link
Contributor

github-actions bot commented Feb 4, 2024

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
For general questions, we recommend using StackOverflow or our discord server.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants