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] Indicate transaction type on service overview #83663

Closed
smith opened this issue Nov 18, 2020 · 5 comments · Fixed by #86143
Closed

[APM] Indicate transaction type on service overview #83663

smith opened this issue Nov 18, 2020 · 5 comments · Fixed by #86143
Assignees
Labels
apm:service-overview Team:APM All issues that need APM UI Team support v7.11.0

Comments

@smith
Copy link
Contributor

smith commented Nov 18, 2020

All data on the service overview page (#81135) should be scoped to a single transaction type. Currently this is the case, but there is no indication to the user that this is what they're looking at.

Either provide an informative indicator or a way of choosing the transaction type viewed on the service overview page.

@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui (Team:apm)

@formgeist
Copy link
Contributor

I've been thinking quite a bit about where it would make sense to indicate the transaction type. We should have it in a place where it indicates that we're scoping the page specifically for those preferred types, but also be able to show the transaction type if none of the preferred are available. The experience here should also be improved to show a callout that indicates that the Overview page is scoped to request or page-load and that the charts are in some cases not available because the data is dependent on those types.

Here are some mocks of where I'd like to take it. I understand that the customization of the search bar might be difficult to accomplish. It is meant to only show on the Overview page in this variation. Additionally, the callout only shows if none of the preferred types are available. Need better copy there.

Screenshot 2020-12-15 at 10 52 14

Screenshot 2020-12-15 at 10 57 03

@elastic/apm-ui @alex-fedotyev

@smith
Copy link
Contributor Author

smith commented Dec 15, 2020

These are fine, but my first reaction is, "Why can't I change it?"

@sorenlouv
Copy link
Member

These are fine, but my first reaction is, "Why can't I change it?"

Yeah, I keep coming back to this too.
It's a balance between making the UI simple and hide irrelevant stuff vs catering for less common user flows.
If we can solve both (simplicity and flexibility) that would be ideal.

@formgeist
Copy link
Contributor

We've decided to define it as such - this is the best solution I can come up with at this time that implies the transaction type is selected for all the contents below.

@formgeist formgeist removed their assignment Dec 16, 2020
ogupte added a commit to ogupte/kibana that referenced this issue Dec 16, 2020
ogupte added a commit to ogupte/kibana that referenced this issue Dec 16, 2020
ogupte added a commit that referenced this issue Dec 17, 2020
ogupte added a commit to ogupte/kibana that referenced this issue Dec 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
apm:service-overview Team:APM All issues that need APM UI Team support v7.11.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants