-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
feat(explore): Linking to spans in traceview from all tables #78984
Conversation
Bundle ReportChanges will increase total bundle size by 7.55kB (0.02%) ⬆️. This is within the configured threshold ✅ Detailed changes
|
❌ 2 Tests Failed:
View the top 2 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets make sure old links still work and keep a fallback to eventId which we can probably fully remove this in a couple of weeks.
There's no concept of `transaction.id` in eap. We now have access to `transaction.span_id` in both EAP and Indexed datasets. This PR enables sending `transaction.span_id` as `targetId` to the `events_trace` endpoint to ensure the transaction is always included in the response. Not the most proud of this solution, will follow up with PRs to completely replace `eventId`=`transaction.id` with `targetId`=`transaction.span_id`. PR also enables finding transactions by their span_ids in the trace view. With this change we can successfully scroll to spans and txns in the traceview from all explore tables using only span_ids. --------- Co-authored-by: Abdullah Khan <[email protected]>
There's no concept of
transaction.id
in eap. We now have access totransaction.span_id
in both EAP and Indexed datasets.This PR enables sending
transaction.span_id
astargetId
to theevents_trace
endpoint to ensure the transaction is always included in the response. Not the most proud of this solution, will follow up with PRs to completely replaceeventId
=transaction.id
withtargetId
=transaction.span_id
.PR also enables finding transactions by their span_ids in the trace view. With this change we can successfully scroll to spans and txns in the traceview from all explore tables using only span_ids.