[ResponseOps] experiment: make all alert doc updates partial

[pmuellr]

work in progress

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: fadf8a7
• Interpreting CI Failures
• Kibana Serverless Image: docker.elastic.co/kibana-ci/kibana-serverless:pr-165275-fadf8a792ef2

Failed CI Steps

• Jest Tests #6
• Jest Tests #16
• FTR Configs #3
• FTR Configs #3
• FTR Configs #32
• FTR Configs #32
• Serverless Security Cypress Tests #7
• Serverless Security Explore Cypress Tests #2

Test Failures

• [job] [logs] Jest Tests #16 / Alerts Client using aliases for alert indices persistAlerts() should not update ongoing alerts in existing index when they are not in the processed alerts
• [job] [logs] Jest Tests #16 / Alerts Client using aliases for alert indices persistAlerts() should recover recovered alerts in existing index
• [job] [logs] Jest Tests #16 / Alerts Client using aliases for alert indices persistAlerts() should update ongoing alerts in existing index
• [job] [logs] Jest Tests #16 / Alerts Client using aliases for alert indices setAlertData() should successfully update context and payload for ongoing alert
• [job] [logs] Jest Tests #16 / Alerts Client using aliases for alert indices setAlertData() should successfully update context and payload for recovered alert
• [job] [logs] Jest Tests #16 / Alerts Client using data streams for alert indices persistAlerts() should not update ongoing alerts in existing index when they are not in the processed alerts
• [job] [logs] Jest Tests #16 / Alerts Client using data streams for alert indices persistAlerts() should recover recovered alerts in existing index
• [job] [logs] Jest Tests #16 / Alerts Client using data streams for alert indices persistAlerts() should update ongoing alerts in existing index
• [job] [logs] Jest Tests #16 / Alerts Client using data streams for alert indices setAlertData() should successfully update context and payload for ongoing alert
• [job] [logs] Jest Tests #16 / Alerts Client using data streams for alert indices setAlertData() should successfully update context and payload for recovered alert
• [job] [logs] Jest Tests #6 / createLifecycleExecutor set flapping on the document updates documents with flapping for active alerts
• [job] [logs] Jest Tests #6 / createLifecycleExecutor set flapping on the document updates existing documents for recovered alerts
• [job] [logs] Jest Tests #6 / createLifecycleExecutor set maintenance window ids on the document does not update documents with maintenance window ids for recovered alerts
• [job] [logs] Jest Tests #6 / createLifecycleExecutor set maintenance window ids on the document does not update documents with maintenance window ids for repeatedly firing alerts
• [job] [logs] Jest Tests #6 / createLifecycleExecutor updates existing documents for recovered alerts
• [job] [logs] Jest Tests #6 / createLifecycleExecutor updates existing documents for repeatedly firing alerts
• [job] [logs] Jest Tests #6 / createLifecycleRuleTypeFactory with a new rule when alerts recover writes the correct alerts
• [job] [logs] FTR Configs #32 / endpoint App level Endpoint functionality from Timeline should show Isolation action in alert details
• [job] [logs] FTR Configs #32 / endpoint App level Endpoint functionality from Timeline should show Isolation action in alert details
• [job] [logs] FTR Configs #3 / Synthetics API Tests SyncGlobalParams added an integration for previously added monitor
• [job] [logs] FTR Configs #3 / Synthetics API Tests SyncGlobalParams added an integration for previously added monitor

Metrics [docs]

Canvas Sharable Runtime

The Canvas "shareable runtime" is an bundle produced to enable running Canvas workpads outside of Kibana. This bundle is included in third-party webpages that embed canvas and therefor should be as slim as possible.

id	before	after	diff
module count	-	5580	+5580
total size	-	6.0MB	+6.0MB

History

• 💔 Build #155267 failed 4e916f6
• 💔 Build #155026 failed 61c6a4b4a9db7858158cab8f76c0e1106daa2a53
• 💚 Build #155013 succeeded ce72bfd638a4ec8f925358cb312da24cd7f7eed1

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream