[Synthetics] Add recovery mode switch for status alerts #229962
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cesco-f
added
release_note:enhancement
backport:skip
botelastic
bot
added
the
Team:actionable-obs
Contributor
|
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
github-actions
bot
added
the
author:obs-ux-management
pmuellr
approved these changes
Jul 30, 2025
Contributor
pmuellr
left a comment
pmuellr
left a comment
There was a problem hiding this comment.
ResponseOps changes LGTM. Thanks for the feature flag / intermediate release aspects!
I'm not sure of OAS docs need to be changed because of this, I think I do often see changes there ...
Contributor
Author
cesco-f
force-pushed
the
recover-first-up
branch
from
895c506 to
7cb2c47
Compare
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8947[❌] x-pack/solutions/observability/test/api_integration_deployment_agnostic/feature_flag_configs/serverless/oblt.serverless.config.ts: 0/25 tests passed. |
Contributor
Author
|
I don't think the failed flaky test run has something to do with changes in this PR. |
shahzad31
reviewed
Aug 4, 2025
src/platform/packages/shared/response-ops/rule_params/synthetics_monitor_status/v1.ts
Outdated
Show resolved
Hide resolved
cesco-f
force-pushed
the
recover-first-up
branch
from
23431cd to
6a264ec
Compare
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
History
|
3 tasks
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
This PR is to improve how we recover monitor status alerts, issue elastic#193613 . It does not close the issue, it is currently disabled because of the [intermediate release process](https://docs.google.com/document/d/1mU5jlIfCKyXdDPtEzAz1xTpFXFCWxqdO5ldYRVO_hgM). [This commit](elastic@dc00912) has to be reverted to enable the feature and it will be done in a separate PR. The user will now be able to select how they want to recover the alert, either when the monitor is back up or when the condition is no longer met. For example, with the current implementation if the rule is "is down 1 time in the past 24 hours" it won't recover until there are 0 downs in the past 24 hours. Enabling this option will make the monitor recover as soon as a UP monitor is received. **Acceptance criteria:** Users have the option where to specify when the recovery should occur: - The first UP test comes in ✅ - The alert condition is no longer met ✅ - Default is the first UP test ✅ **Screenshot:** <img width="1512" height="825" alt="Screenshot 2025-07-30 at 15 06 46" src="https://github.com/user-attachments/assets/110ca4ac-e259-4bdf-9c41-b55feda95aed" /> **Video:** https://github.com/user-attachments/assets/5c0f6d10-caf8-47e7-a206-fe616f130fca --------- Co-authored-by: Shahzad <shahzad31comp@gmail.com>
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
This PR is to improve how we recover monitor status alerts, issue elastic#193613 . It does not close the issue, it is currently disabled because of the [intermediate release process](https://docs.google.com/document/d/1mU5jlIfCKyXdDPtEzAz1xTpFXFCWxqdO5ldYRVO_hgM). [This commit](elastic@dc00912) has to be reverted to enable the feature and it will be done in a separate PR. The user will now be able to select how they want to recover the alert, either when the monitor is back up or when the condition is no longer met. For example, with the current implementation if the rule is "is down 1 time in the past 24 hours" it won't recover until there are 0 downs in the past 24 hours. Enabling this option will make the monitor recover as soon as a UP monitor is received. **Acceptance criteria:** Users have the option where to specify when the recovery should occur: - The first UP test comes in ✅ - The alert condition is no longer met ✅ - Default is the first UP test ✅ **Screenshot:** <img width="1512" height="825" alt="Screenshot 2025-07-30 at 15 06 46" src="https://github.com/user-attachments/assets/110ca4ac-e259-4bdf-9c41-b55feda95aed" /> **Video:** https://github.com/user-attachments/assets/5c0f6d10-caf8-47e7-a206-fe616f130fca --------- Co-authored-by: Shahzad <shahzad31comp@gmail.com>
cesco-f
added a commit
that referenced
this pull request
Aug 20, 2025
qn895
pushed a commit
to qn895/kibana
that referenced
this pull request
Aug 26, 2025
…elastic#231091) This PR is a follow up of elastic#229962 and it closes elastic#193613 . It can be merged only after [this commit](elastic@933d2ba) has been included in a serverless release.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is to improve how we recover monitor status alerts, issue #193613 .
It does not close the issue, it is currently disabled because of the intermediate release process.
This commit has to be reverted to enable the feature and it will be done in a separate PR.
The user will now be able to select how they want to recover the alert, either when the monitor is back up or when the condition is no longer met.
For example, with the current implementation if the rule is "is down 1 time in the past 24 hours" it won't recover until there are 0 downs in the past 24 hours.
Enabling this option will make the monitor recover as soon as a UP monitor is received.
Acceptance criteria:
Users have the option where to specify when the recovery should occur:
Screenshot:
Video:
Screen.Recording.2025-07-29.at.16.24.20.mov