Skip to content

Conversation

doakalexi
Copy link
Contributor

Summary

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

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

  • 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
  • If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
  • This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
  • Flaky Test Runner was used on any tests changed
  • The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
  • Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 3, 2025

🤖 Jobs for this PR can be triggered through checkboxes. 🚧

ℹ️ To trigger the CI, please tick the checkbox below 👇

  • Click to trigger kibana-pull-request for this PR!
  • Click to trigger kibana-deploy-project-from-pr for this PR!
  • Click to trigger kibana-deploy-cloud-from-pr for this PR!

@elasticmachine
Copy link
Contributor

elasticmachine commented Oct 3, 2025

⏳ Build in-progress, with failures

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #44 / Alerting alerts_as_data install alerts as data resources should install context specific alerts as data resources on startup
  • [job] [logs] FTR Configs #44 / Alerting alerts_as_data install alerts as data resources should install context specific alerts as data resources on startup
  • [job] [logs] FTR Configs #19 / alerting api integration security and spaces enabled Alerts - Group 5 bulk untrack by query no_kibana_privileges at space1 should bulk mark alerts as untracked by query
  • [job] [logs] FTR Configs #19 / alerting api integration security and spaces enabled Alerts - Group 5 bulk untrack by query no_kibana_privileges at space1 should bulk mark alerts as untracked by query
  • [job] [logs] FTR Configs #78 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations "after each" hook for "returns the information necessary to finalize the migration"
  • [job] [logs] FTR Configs #78 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations "after each" hook for "returns the information necessary to finalize the migration"
  • [job] [logs] FTR Configs #78 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations returns the information necessary to finalize the migration
  • [job] [logs] FTR Configs #78 / Alerts and alerts index related logic - Basic License/Essentials Tier ESS specific alerts and alert index logic ESS specific alerts index migration logic @ess Creating signals migrations returns the information necessary to finalize the migration
  • [job] [logs] Jest Tests #15 / Alerts Service using aliases for alert indices register() should correctly install resources for custom namespace on demand when isSpaceAware is true
  • [job] [logs] Jest Tests #15 / Alerts Service using aliases for alert indices register() should correctly install resources for custom namespace on demand when isSpaceAware is true
  • [job] [logs] FTR Configs #95 / cases security and spaces enabled: trial Common update_alert_status "before each" hook for "should update the status of multiple alerts attached to multiple cases using the cases client"
  • [job] [logs] FTR Configs #95 / cases security and spaces enabled: trial Common update_alert_status "before each" hook for "should update the status of multiple alerts attached to multiple cases using the cases client"
  • [job] [logs] FTR Configs #9 / cases security and spaces enabled: trial push_case memoryless server alerts "before each" hook for "should change the status of all alerts attached to a case to closed when closure_type: close-by-pushing and syncAlerts: true"
  • [job] [logs] FTR Configs #9 / cases security and spaces enabled: trial push_case memoryless server alerts "before each" hook for "should change the status of all alerts attached to a case to closed when closure_type: close-by-pushing and syncAlerts: true"
  • [job] [logs] FTR Configs #23 / Session View API (basic) Session view - /internal/session_view/process_events - with a basic license using typical process event data "before all" hook for "/internal/session_view/process_events fails when an invalid api version is specified"
  • [job] [logs] FTR Configs #23 / Session View API (basic) Session view - /internal/session_view/process_events - with a basic license using typical process event data "before all" hook for "/internal/session_view/process_events fails when an invalid api version is specified"

History

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants