-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Comments
Pinging @elastic/apm-ui (Team:apm) |
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 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. @elastic/apm-ui @alex-fedotyev |
These are fine, but my first reaction is, "Why can't I change it?" |
Yeah, I keep coming back to this too. |
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. |
…ervice overview (elastic#86143)
…overview (#86143) (#86200) Co-authored-by: Kibana Machine <[email protected]>
…ervice overview (elastic#86143)
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.
The text was updated successfully, but these errors were encountered: