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

Have an option to enable TCP connection details in tracing. #5057

Open
Samjin opened this issue Apr 30, 2024 · 2 comments
Open

Have an option to enable TCP connection details in tracing. #5057

Samjin opened this issue Apr 30, 2024 · 2 comments
Labels
component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. raised by user

Comments

@Samjin
Copy link

Samjin commented Apr 30, 2024

Is your feature request related to a problem? Please describe.
image

We'd like to be able to see what happened before POST /graphql span, how long it takes for TCP, DNS to establish the connection. This will be helpful to know if any optimization can be done for connection pool, keep alive sockets, dns cache etc.

Describe the solution you'd like
Have a option to turn the feature on so user can observe the details in trace and create monitors.

@abernix abernix added the component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. label May 6, 2024
@abernix
Copy link
Member

abernix commented May 13, 2024

Are you talking about the connectivity between the client and the router or the router and the subgraphs?

@Samjin
Copy link
Author

Samjin commented May 13, 2024

Are you talking about the connectivity between the client and the router or the router and the subgraphs?

Router to subgraphs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/open-telemetry OTLP, Datadog, Prometheus, etc. and the integrations around it. raised by user
Projects
None yet
Development

No branches or pull requests

2 participants