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

nginx span shorter than upstream server span #459

Open
naseemkullah opened this issue Jun 14, 2024 · 0 comments
Open

nginx span shorter than upstream server span #459

naseemkullah opened this issue Jun 14, 2024 · 0 comments
Labels

Comments

@naseemkullah
Copy link
Member

Describe your environment Describe any aspect of your environment relevant to the problem, including your platform, build system, version numbers of installed dependencies, etc. If you're reporting a problem with a specific version of a library in this repo, please check whether the problem has been fixed on main branch.

nginx-ingress-controller on k8s, opentelemetry enabled
backend nodejs service in same k8s cluster, opentelemetry enabled

Steps to reproduce
setup an env as per above

What is the expected behavior?
that the nginx span is a little longer than the upstream backend span, accounting for the network hop and what not

What is the actual behavior?
its often exactly the same length (e.g. both are 500ms) or even more bizarre, sometimes the nginx span is shorter by a few ms

image

Additional context
Wondering if it has to do with where the span starts and ends within this codebase

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant