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

[APM] Link to related errors from Transaction detail page #21920

Closed
formgeist opened this issue Aug 13, 2018 · 2 comments
Closed

[APM] Link to related errors from Transaction detail page #21920

formgeist opened this issue Aug 13, 2018 · 2 comments
Assignees
Labels
Team:APM All issues that need APM UI Team support v7.0.0

Comments

@formgeist
Copy link
Contributor

Fixes #20981

Summary

Since we have the transaction.id available for both transaction and errors, we can now show related errors to a specific transaction. Since a single transaction can have multiple errors related to itself, we want to link to a filtered error groups view first so the user gets an overview of the related errors.

Design

Show amount of related errors on the KPI content area for transaction sample
apm-transaction-detail.png

Filtered result on the errors overview page for a specific transaction.id
apm-errors-list-filtered.png

@formgeist formgeist added Team:APM All issues that need APM UI Team support [zube]: Inbox labels Aug 13, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@jasonrhodes
Copy link
Member

Note: look into abstracting the logic for creating the kuery bar link

@ogupte ogupte self-assigned this Jan 14, 2019
ogupte added a commit to ogupte/kibana that referenced this issue Jan 24, 2019
ogupte added a commit to ogupte/kibana that referenced this issue Jan 29, 2019
 - linking to errors list filtered by current transaction id
 - including the error count in the transaction details link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:APM All issues that need APM UI Team support v7.0.0
Projects
None yet
Development

No branches or pull requests

7 participants