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] ML results should always be displayed if service has one environment #86775

Closed
Tracked by #109787
dgieselaar opened this issue Dec 22, 2020 · 5 comments
Closed
Tracked by #109787

[APM] ML results should always be displayed if service has one environment #86775

dgieselaar opened this issue Dec 22, 2020 · 5 comments
Assignees
@dgieselaar
Labels
apm:environments Issues about the "environment" field in APM UI bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support

Comments

@dgieselaar
Copy link
Member

Currently, we only show ML results on the service overview/transactions pages if one environment has been selected. By default, we select "All". This means that in a common scenario where a service has one environment, we make it hard for the user to see ML results. We should fix this, for example by always showing ML results if the service has one environment.
@dgieselaar dgieselaar added bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support v7.11.0 labels Dec 22, 2020
@elasticmachine
Copy link
Contributor

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

@dgieselaar dgieselaar mentioned this issue Dec 22, 2020
Closed
@sorenlouv
Copy link
Member

I agree that this is not great atm. For 7.12 I hope we can finally remove the "All environments" option which should solve this.

@zube zube bot added the [zube]: 7.11 label Jan 4, 2021
@zube
Copy link

zube bot commented Jan 4, 2021

dgieselaar said: Let's try to fix this but only if low risk.

@smith smith self-assigned this Jan 5, 2021
smith added a commit to smith/kibana that referenced this issue Jan 5, 2021
@smith
Show ML jobs on chart when only one environment
510acdd 
Make it so if you're looking at the latency chart for a service with only one environment, while the environment selector is set to "All", it uses the single environment so the ML will be shown.

It does this by overriding the uiFilters in this case.

Rename the exported function from use_transaction_latency_chart_fetcher to match the file name.

Fixes elastic#86775.
@smith smith mentioned this issue Jan 5, 2021
Closed
@smith smith assigned dgieselaar and unassigned smith Jan 6, 2021
dgieselaar added a commit to dgieselaar/kibana that referenced this issue Jan 19, 2021
@dgieselaar
[APM] Display ML results when there's one environment
de010fa 
Closes elastic#86775.
@dgieselaar dgieselaar mentioned this issue Jan 19, 2021
Closed
@formgeist
Copy link
Contributor

@sqren I think this got deprioritized around the 7.11 release but it's still a rather big UX issue that the health status on the inventory page is indicating critical status but the ML anomalies are not showing because we're not opting to show any job results no matter what environment selected. Do you think it's worth looking into just fixing this issue rather than relying on us to change the environment picker functionality?

@smith smith added the apm:environments Issues about the "environment" field in APM UI label Jul 16, 2021
@formgeist formgeist mentioned this issue Aug 24, 2021
Open
10 tasks
@dgieselaar dgieselaar mentioned this issue Sep 17, 2021
Closed
@dgieselaar dgieselaar mentioned this issue Nov 25, 2021
Merged
@dgieselaar
Copy link
Member Author

Closed by #119709.

@zube zube bot removed the [zube]: Done label Mar 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dgieselaar dgieselaar

Labels
apm:environments Issues about the "environment" field in APM UI bug Fixes for quality problems that affect the customer experience Team:APM All issues that need APM UI Team support
Projects
None yet
Milestone
No milestone
5 participants
@smith @sorenlouv @dgieselaar @formgeist @elasticmachine