[Logs UI][Test Scenario] Log threshold alerts (general)

[mgiota]

Summary

This test scenario covers general log threshold alert functionality.

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

General

• Alerts can be added from within the logs application
• Alerts can be added from the alerts management page (/app/management/insightsAndAlerting/triggersActions/alerts)
• Alerts can be edited from the alerts management page (/app/management/insightsAndAlerting/triggersActions/alerts)
• Documentation exists, is comprehensive, and makes sense (https://www.elastic.co/guide/en/observability/master/logs-threshold-alert.html) 🆕

Action configuration

• timestamp can be accessed and used as part of the actions configuration 🆕

Change history

7.14.0 (this)

• Performance improvements and a UI warning when a group by has been set with an unoptimised comparator ([Logs UI] Log threshold rule performance improvements #102650)

7.10.0

• Added chart previews ([Logs UI] Log alerts chart previews #75296)
• Added ratio configurations ([Logs UI] Log threshold ratio alerts #76867)
• Added timestamp context variable ([Logs UI] Add timestamp as a context variable to log threshold alerts #78932)

7.9.0 (#974)

• Added support for "group by" in logs alerts ([Logs UI] [Alerting] "Group by" functionality #68250)

7.8.0 (#849)

• Added initial logs alerts implementation ([Logs UI] Alerting #62806)

[elasticmachine]

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

[mgiota]

LGTM