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 app page title should reflect what's showing #41456
Comments
Pinging @elastic/apm-ui |
I see two use cases here:
I currently have 20+ open tabs 😋- so the title should start with the most differential part in my opinion. What about: Which would mean: @hbharding I would also like to hear your opinion. |
Yeah, that's exactly the rationale, on both counts. |
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on #41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes #41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on elastic#41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes elastic#41456.
Instead of using only the text of the last breadcrumb for the page title, use the breadcrumbs to create a reverse list of items (since in the page title we want the most relevant item at the beginning) that are pipe-separated. This only affects the page titles in APM, since Infra uses a different mechanism for breadcrumbs and page titles. The implementation doesn't exactly match the discussion on #41456, and there's no truncation, but it should be an improvement. Also update the tests so that they more accurately reflect the routes actually being used in the app. Fixes #41456.
Currently the APM app only shows the last breadcrumb as the page title (in the tab list, for example).
Describe the feature:
The page title should be reflective of the App & any specialization being shown, similar to the Infra app, which indicates what it's showing:
Infrastructure | Inventory - Kibana
Infrastructure | Metrics Explorer - Kibana
Perhaps the APM App can show:
APM | Services - Kibana
(when on the base page)APM | <Service> - Kibana
(when on a named service) - examplesAPM | opbeans-python | Transactions - Kibana
)APM | opbeans-python | Transactions | GET opbeans.views.home - Kibana
)APM | opbeans-python | Errors - Kibana
)Describe a specific use case for the feature:
It's not at all uncommon to have multiple tabs or pages open- with multiple APM app tabs open they might all just say "Transactions" or "Errors", without knowing which is which.
The text was updated successfully, but these errors were encountered: