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

[Log UI] Move UI warning in the log threshold rule type closer to the group by section #106219

Closed
mgiota opened this issue Jul 20, 2021 · 3 comments
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"

Comments

@mgiota
Copy link
Contributor

mgiota commented Jul 20, 2021

While testing #104354 on cloud 7.14 the UI warning appeared
screenshot but I would expect it to appear above the Query A and Query B sections. I had to scroll down to realize that the warning was indeed there.

Acceptance criteria
Consider if it makes sense to move it closer to the Group by section

How to test
Create a log threshold rule type and set a group by with an unoptimised comparator (anything that can evaluate 0 as a threshold). For more details have a look at the the PR that introduced the UI warning #102650

@mgiota mgiota added the Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services label Jul 20, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/logs-metrics-ui (Team:logs-metrics-ui)

@miltonhultgren miltonhultgren added Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge" and removed Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services labels Jun 23, 2023
@elasticmachine
Copy link
Contributor

Pinging @elastic/actionable-observability (Team: Actionable Observability)

@maryam-saeidi
Copy link
Member

Will be fixed in the new combined threshold rule: https://github.com/elastic/actionable-observability/issues/36

@maryam-saeidi maryam-saeidi closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team: Actionable Observability - DEPRECATED For Observability Alerting and SLOs use "Team:obs-ux-management", for AIops "Team:obs-knowledge"
Projects
None yet
Development

No branches or pull requests

4 participants