[Synthetics] Add monitor downtime alert on no data
This issue closes #197923.
A new switch has been added when creating a monitor status rule to get alerts on pending monitors:
Getting alerts on no data video:
https://github.com/user-attachments/assets/f353251d-bae9-4c34-971b-74b777cb5400
Switching off the option and checking that the alert recovers video:
https://github.com/user-attachments/assets/437ea21e-5708-4c1e-9de8-bc10ae390324
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
:robot: GitHub comments
Expand to view the GitHub comments
Just comment with:
/oblt-deploy: Deploy a Kibana instance using the Observability test environments.rundocs-build: Re-trigger the docs validation. (use unformatted text in the comment!)
Flaky Test Runner Stats
🟠 Some tests failed. - kibana-flaky-test-suite-runner#8377
[❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/stateful/oblt.stateful.config.ts: 0/25 tests passed. [❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/serverless/oblt.serverless.config.ts: 0/25 tests passed.
Flaky Test Runner Stats
🟠 Some tests failed. - kibana-flaky-test-suite-runner#8379
[❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/stateful/oblt.stateful.config.ts: 0/25 tests passed.
Flaky Test Runner Stats
🟠 Some tests failed. - kibana-flaky-test-suite-runner#8411
[❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/stateful/oblt.stateful.config.ts: 0/25 tests passed.
:yellow_heart: Build succeeded, but was flaky
- Buildkite Build
- Commit: 8255d04f8f146a332cedee752eb5801f37d5de7c
- Kibana Serverless Image:
docker.elastic.co/kibana-ci/kibana-serverless:pr-220127-8255d04f8f14
Failed CI Steps
Test Failures
- [job] [logs] FTR Configs #58 / alerting api integration security and spaces enabled - Group 2 Connectors execute space_1_all at space1 should log api key information from execute request
Metrics [docs]
Async chunks
Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app
| id | before | after | diff |
|---|---|---|---|
synthetics |
1.0MB | 1.0MB | +747.0B |
History
- :green_heart: Build #309960 succeeded e8bd805ddf583b074852f84d43d86ac71adc25cf
- :broken_heart: Build #309784 failed 8acb51b005f111a9d8437a8d5c00e9a42d2481ee
- :green_heart: Build #308732 succeeded c73416181436b805d8b4813450b7cb6660000525
- :green_heart: Build #308639 succeeded d01402b8a9b5c59be1bdcd72ff154779b4d17c89
- :green_heart: Build #308263 succeeded ebcc97db0158b33073c2d085c3b30d3624130373
cc @shahzad31
Flaky Test Runner Stats
🟠 Some tests failed. - kibana-flaky-test-suite-runner#8416
[❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/stateful/oblt.stateful.config.ts: 0/25 tests passed.
Flaky Test Runner Stats
🟠 Some tests failed. - kibana-flaky-test-suite-runner#8417
[❌] x-pack/test/api_integration/deployment_agnostic/feature_flag_configs/stateful/oblt.stateful.config.ts: 0/25 tests passed.
Starting backport for target branches: 8.19
https://github.com/elastic/kibana/actions/runs/15757837319
💔 All backports failed
| Status | Branch | Result |
|---|---|---|
| ❌ | 8.19 | Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - [SKA] relocate alerting_api_integration tests (#222603) |
Manual backport
To create the backport manually run:
node scripts/backport --pr 220127
Questions ?
Please refer to the Backport tool documentation
💚 All backports created successfully
| Status | Branch | Result |
|---|---|---|
| ✅ | 8.19 |
Note: Successful backport PRs will be merged automatically after passing CI.
Questions ?
Please refer to the Backport tool documentation