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 (count configuration) #104353

Closed
16 tasks done
mgiota opened this issue Jul 5, 2021 · 1 comment
Closed
16 tasks done

[Logs UI] [Test Scenario] Log threshold alerts (count configuration) #104353

mgiota opened this issue Jul 5, 2021 · 1 comment
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 count 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

  • The count can be configured with multiple comparators
  • 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
  • Group by
    • One grouping can be set
    • Multiple groupings can be set
    • Groupings 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 🆕
    • When a threshold is configured this is displayed on the chart preview 🆕
  • UI warning when a group by has been set
    • a UI warning appears when using unoptimised (anything that can evaluate 0 as a threshold) threshold comparators
    • no UI warning appears when using the more than comparator for the threshold

Triggering

  • Alerts should fire when the configured condition(s) are met

Change history

7.14.0 (this)

7.10.0

7.9.0 (#974)

7.8.0 (#849)

@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 5, 2021
@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)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Jul 5, 2021
@mgiota mgiota added the Feature:Logs UI Logs UI feature label Jul 5, 2021
@mgiota mgiota self-assigned this Jul 5, 2021
@mgiota mgiota closed this as completed Jul 20, 2021
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