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

Navigating across links in Traces tab doesn't appear to work #6771

Open
1 task done
eerhardt opened this issue Nov 22, 2024 · 1 comment · May be fixed by #6773
Open
1 task done

Navigating across links in Traces tab doesn't appear to work #6771

eerhardt opened this issue Nov 22, 2024 · 1 comment · May be fixed by #6773
Assignees
Milestone

Comments

@eerhardt
Copy link
Member

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

When Traces have "Link" and "Backlinks", navigating to these linked traces doesn't navigate to the linked issue. The dashboard stays at the current trace.

Expected Behavior

I expect the linked trace to be shown in the dashboard.

Steps To Reproduce

  1. Checkout Add RabbitMQ.Client v7 client integration package #6770, which adds support for RabbitMQ v7. The traces emitted from this new version have links instead of parent-child relationships between traces.
  2. Run the TestShop playground app.
  3. Add an item to the basket and click the "cart" button to checkout
  4. In the Dashboard, navigate to the trace for the orderprocessor that received the message
  5. At the bottom of that trace, find the linked trace that sent the message and click "View"

Image

Exceptions (if any)

No response

.NET Version info

No response

Anything else?

cc @JamesNK

@JamesNK JamesNK self-assigned this Nov 23, 2024
@JamesNK JamesNK added this to the 9.1 milestone Nov 23, 2024
@JamesNK
Copy link
Member

JamesNK commented Nov 23, 2024

I can repo it. Links between spans in one trace work, but links between spans in different traces is broken.

@JamesNK JamesNK linked a pull request Nov 23, 2024 that will close this issue
18 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants