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

[Logs UI] [Test Scenario] Log threshold alerts (ratio configuration) #104354

Closed
14 tasks done
mgiota opened this issue Jul 5, 2021 · 3 comments
Closed
14 tasks done

[Logs UI] [Test Scenario] Log threshold alerts (ratio configuration) #104354

mgiota opened this issue Jul 5, 2021 · 3 comments
Assignees
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services

Comments

@mgiota
Copy link
Contributor

mgiota commented Jul 5, 2021

Summary

This test scenario covers ratio configurations for log threshold alerts.

Test requirements

Testing of alerting requires SSL. You can enable this with:

  • yarn start --ssl
  • yarn es snapshot --ssl
  • ssl.verification_mode: none within the Filebeat configuration

There are also enhanced details here: https://github.com/elastic/observability-dev/issues/849#issuecomment-626770782.

Test cases

Configuration

  • For both Query A and Query B: 🆕

    • Condition comparators should change based on the field type (numeric fields, aggregatable fields, and non-aggregatable fields should yield compatible comparators)
    • Multiple conditions can be added
    • Conditions can be removed
    • A chart preview can be toggled for each condition 🆕
      • This chart should be collapsed by default 🆕
      • Previews change based on whether a group by is set 🆕
  • Group by

    • One grouping can be set
    • Multiple groupings can be set
    • Groupings can be removed
  • UI warning when a group by has been set

    • no UI warning appears when using the more than comparator for the threshold
    • a UI warning appears when using unoptimised (anything that can evaluate 0 as a threshold) threshold

Triggering

  • Alerts should fire when the configured ratio threshold is met 🆕

Change history

7.14.0 (this)

7.10.0

7.9.0 (#974)

7.8.0 (#849)

@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 5, 2021
@elasticmachine
Copy link
Contributor

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

@mgiota mgiota self-assigned this Jul 5, 2021
@mgiota mgiota added the Feature:Logs UI Logs UI feature label Jul 5, 2021
@mgiota mgiota assigned mgiota and unassigned mgiota Jul 5, 2021
@mgiota
Copy link
Contributor Author

mgiota commented Jul 5, 2021

Regarding the UI warning
I used a less than comparator and the warning indeed appeared 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.

Shall we consider moving it closer to the Group by section?

Screenshot 2021-07-05 at 23 34 19

Screenshot 2021-07-05 at 23 34 32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Logs UI Logs UI feature Team:Infra Monitoring UI - DEPRECATED DEPRECATED - Label for the Infra Monitoring UI team. Use Team:obs-ux-infra_services
Projects
None yet
Development

No branches or pull requests

2 participants