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.

Sign up for GitHub

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

Jump to bottom

[APM] Filters: Technical prerequisites before adding Local Filters #40416

Closed
formgeist opened this issue Jul 5, 2019 · 2 comments
Closed

[APM] Filters: Technical prerequisites before adding Local Filters #40416

formgeist opened this issue Jul 5, 2019 · 2 comments
Labels
Meta Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture v7.4.0

Comments

@formgeist
Copy link
Contributor

formgeist commented Jul 5, 2019 •
edited
Loading

Blocked by #40236 and other design related implementations

Summary

Before we implement the proposed Local filters in the APM UI, we need to make a plan for how we intend to perhaps restructure views and queries in order to keep a lean UI.

Related issues
@formgeist formgeist added Meta Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture labels Jul 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/apm-ui

@formgeist
Copy link
Contributor Author

Discussed with @sqren and @dgieselaar in Zoom that we need to finalize the short-term incoming design changes to the header (#40236) and others before diving into refactoring the views. I've considered this blocked until those design issues are cleared.

cc @graphaelli

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Meta Team:APM All issues that need APM UI Team support technical debt Improvement of the software architecture and operational architecture v7.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@graphaelli @sorenlouv @formgeist @elasticmachine