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

Merge Gateway Tracing Root Trace service name random #3210

Closed
owenhaynes opened this issue Apr 16, 2024 · 2 comments · Fixed by #3214
Closed

Merge Gateway Tracing Root Trace service name random #3210

owenhaynes opened this issue Apr 16, 2024 · 2 comments · Fixed by #3214
Assignees
Labels
area/translator Issues related to Gateway's translation service, e.g. translating Gateway APIs into the IR. kind/bug Something isn't working

Comments

@owenhaynes
Copy link
Contributor

Description:
Traces that are emitted when using merge gateway have a random gateway name as the service name. They do not use the correct gateway name that the route is attached to.

Repro steps:

Run merge gateway with multiple gateways with named listeners with routes attached. You should notice pretty quickly that the service name does not match up with the gateway that the route and host belongs to

Environment:
envoy gateway 1.0.1

@zirain
Copy link
Contributor

zirain commented Apr 17, 2024

cc @cnvergence

@cnvergence
Copy link
Member

thanks for reporting @owenhaynes

@cnvergence cnvergence added kind/bug Something isn't working and removed triage labels Apr 17, 2024
@cnvergence cnvergence added the area/translator Issues related to Gateway's translation service, e.g. translating Gateway APIs into the IR. label Apr 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/translator Issues related to Gateway's translation service, e.g. translating Gateway APIs into the IR. kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants