Suppression/im investigate ftr failures

[vitaliidm]

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
• Flaky Test Runner was used on any tests changed
• 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

[vitaliidm]

/ci

[vitaliidm]

/ci

[vitaliidm]

/ci

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: 0c633b1
• Interpreting CI Failures

Failed CI Steps

• FTR Configs #26
• FTR Configs #26
• FTR Configs #44
• FTR Configs #44
• FTR Configs #55
• FTR Configs #55

Test Failures

• [job] [logs] FTR Configs #26 / Detection rule type telemetry @ess @serverless All task telemetry types generically @skipInQA should only have task metric values when no rules are running
• [job] [logs] FTR Configs #26 / Detection rule type telemetry @ess @serverless All task telemetry types generically @skipInQA should only have task metric values when no rules are running
• [job] [logs] FTR Configs #55 / Entity Analytics - Risk Engine @ess @serverless Risk Scoring Calculation API with auditbeat data @skipInServerless with asset criticality data "before each" hook for "calculates and persists risk scores with additional criticality metadata and modifiers"
• [job] [logs] FTR Configs #55 / Entity Analytics - Risk Engine @ess @serverless Risk Scoring Calculation API with auditbeat data @skipInServerless with asset criticality data "before each" hook for "calculates and persists risk scores with additional criticality metadata and modifiers"
• [job] [logs] FTR Configs #44 / Rule execution logic API Execution logic @ess @serverless EQL type rules with asset criticality should be enriched alert with criticality_level
• [job] [logs] FTR Configs #44 / Rule execution logic API Execution logic @ess @serverless EQL type rules with asset criticality should be enriched alert with criticality_level

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
ruleRegistry	239	241	+2

Unknown metric groups

API count

id	before	after	diff
ruleRegistry	268	270	+2

ESLint disabled in files

id	before	after	diff
securitySolution	72	73	+1

References to deprecated APIs

id	before	after	diff
securitySolution	519	521	+2

Total ESLint disabled count

id	before	after	diff
securitySolution	546	547	+1

History

• 💔 Build #189078 failed c96e6b2
• 💔 Build #189065 failed c96e6b2

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