[Security Solution] Setting a large default rule interval #171814

VidhiRambhia · 2023-11-23T03:28:00Z

Resolves: #153689

Summary

The issue: In many tests we use a short rule execution interval ('5m' or less). This leads to rules getting scheduled for execution many times during a test run. It unnecessarily hogs on CI resources. For most tests we just want a single execution.

This PR:

Sets 24h as the default interval for all rule creation utils used in Cypress tests and in API integration tests
Overrides the default 24h interval for a few tests that need a shorter interval.

…4 hours

VidhiRambhia · 2023-11-30T16:50:49Z

Hi @banderror,

Please let me know your thoughts on this. Thanks!

banderror

Thanks @VidhiRambhia, I reviewed the change and left a comment.

x-pack/test/security_solution_cypress/config.ts

elasticmachine · 2023-11-30T17:05:47Z

Pinging @elastic/security-detections-response (Team:Detections and Resp)

elasticmachine · 2023-11-30T17:05:48Z

Pinging @elastic/security-solution (Team: SecuritySolution)

…4 hours

nikitaindik · 2024-05-29T13:28:47Z

/ci

PhilippeOberti

LGTM for the Threat Hunting team

dhurley14

Approving with the caveat I think with these changes it would be good to see a test case in x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_creation/trial_license_complete_tier/create_rules.ts that removes the interval, creates a rule with no interval defined, and checks that it still defaults to 5m.

dhurley14 · 2024-05-31T16:12:41Z

...sponse/rules_management/rule_bulk_actions/trial_license_complete_tier/perform_bulk_action.ts

@@ -1624,7 +1624,7 @@ export default ({ getService }: FtrProviderContext): void => {
                  {
                    type: BulkActionEditTypeEnum.set_rule_actions,
                    value: {
-                      throttle: '1h',
+                      throttle: '1d',


Is there a preference here for mixing '1d' values with '24h' values? Should we standardize on one vs the other?

I used 24h everywhere, but here it had to be 1d, because throttle has to be on of these

const ThrottleForBulkActions = z.enum(['rule', '1h', '1d', '7d']);

…se-schedule-interval

nikitaindik · 2024-06-03T13:58:45Z

Approving with the caveat I think with these changes it would be good to see a test case in x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_creation/trial_license_complete_tier/create_rules.ts that removes the interval, creates a rule with no interval defined, and checks that it still defaults to 5m.

Thanks @dhurley14! Added in this commit.

MadameSheema

security-engineering-productivity changes LGTM

dplumlee

Thanks for the updates @nikitaindik! Rule management changes lgtm, just left a question

dplumlee · 2024-06-03T15:38:43Z

...tes/detections_response/rules_management/rule_read/trial_license_complete_tier/find_rules.ts

@@ -145,13 +145,17 @@ export default ({ getService }: FtrProviderContext): void => {
      const rule: ReturnType<typeof getSimpleRule> = {
        ...getSimpleRule('rule-1'),
        throttle: '1h', // <-- throttle makes this a scheduled action
+        interval: '50m', // has to be less than "throttle"


Why does this have to be less than throttle here but equal in other places? Just because we're testing action logic?

Actually, you're right. I have re-checked and it looks like we can use 24h in both places.

…se-schedule-interval

banderror · 2024-06-04T13:46:30Z

@elasticmachine merge upstream

banderror · 2024-06-04T13:55:17Z

@elasticmachine run elasticsearch-ci/docs

banderror · 2024-06-04T14:04:08Z

/ci

…kibana into VidhiRambhia_increase-schedule-interval

banderror · 2024-06-04T14:17:52Z

.../security_solution/common/api/detection_engine/model/rule_schema/rule_request_schema.mock.ts

In this file we have mocks with interval == 5m. Is this on purpose?

getUpdateNewTermsSchemaMock - this function seems to be unused. Can we update the interval here to 24h?

getCreateThreatMatchRulesSchemaMock - this one is used, but only from unit tests. Can we update the interval here to 24h?

Thanks! Changed to 24h in both functions in this commit

banderror · 2024-06-04T14:28:25Z

.../security_solution/common/api/detection_engine/model/rule_schema/rule_request_schema.mock.ts

+  interval: '24h',
  from: 'now-6m',


The interval and from fields are tightly coupled. In the app, the from field will always be now - (interval + lookback). Here, the implied lookback was 1 minute before the change to 24h.

I'd suggest to update the from field according to the new interval value in all the places where we're updating the interval in this PR.

Suggested change

interval: '24h',

from: 'now-6m',

interval: '24h', // or 1440 mins

from: 'now-1450m', // lookback of 10 mins in addition to the interval of 1440 mins

We can keep the tests and mocks where from is a constant from the very past, where likely it was done on purpose to be able to read source events with static timestamps (e.g. from an es archive):

interval: '24h', from: '1900-01-01T00:00:00.000Z',

Thanks! Updated in this commit.

banderror · 2024-06-04T15:02:26Z

...n_engine/rule_execution_logic/trial_license_complete_tier/execution_logic/indicator_match.ts

This is a general comment not related to this file. I can still see many instances of the 5-minute interval in test mocks, integration tests, and e2e tests.

Common and server-side mocks:

kibana/x-pack/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_response_schema.mock.ts

Line 48 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/common/api/detection_engine/model/rule_schema/rule_response_schema.mock.ts

Line 167 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/routes/__mocks__/request_responses.ts

Line 367 in 557e61d

schedule: { interval: '5m' },

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/routes/__mocks__/request_responses.ts

Line 520 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/routes/__mocks__/utils.ts

Line 51 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_schema/model/rule_schemas.mock.ts

Line 237 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_types/__mocks__/es_results.ts

Line 501 in 557e61d

interval: '5m',

kibana/x-pack/plugins/security_solution/server/lib/detection_engine/rule_types/__mocks__/rule.ts

Line 28 in 557e61d

interval: '5m',

There are many interval: '5m' instances in the security_solution_api_integration/test_suites/detections_response folder.

There's also one in security_solution_cypress/cypress/e2e/detection_response:

kibana/x-pack/test/security_solution_cypress/cypress/e2e/detection_response/rule_management/prebuilt_rules/prebuilt_rules_preview.cy.ts

Line 145 in 557e61d

interval: '5m',

Finally, there's a lot of them in unit tests.

While these intervals might not be affecting those tests where we create enabled rules and run them, keeping hundreds of interval: '5m' instances in the code seems off, unnecessary and potentially unsafe.

I'd be fine with merging this PR without further large-scale refactoring, if we create a new tech debt ticket for addressing this in the future. As part of this ticket, we might want to consolidate all our rule mocks under security_solution/common/api/detection_engine/model/rule_schema.

banderror · 2024-06-04T15:03:10Z

...n_engine/rule_execution_logic/trial_license_complete_tier/execution_logic/indicator_match.ts

Another general comment: did we run the changed tests in the flaky test runner?

mistic · 2024-06-04T15:58:05Z

buildkite test this

…se-schedule-interval

… `getUpdateNewTermsSchemaMock`

…kibana into VidhiRambhia_increase-schedule-interval

nikitaindik · 2024-06-05T08:25:56Z

Thanks for the feedback @banderror! I'll update "from" values as you suggested, add a new Flaky Test Runner run and will create a ticket for further refactoring. Changing the PR status back to Draft for now.

nikitaindik · 2024-06-05T12:59:51Z

...ites/detections_response/rules_management/rule_creation/trial_license_complete_tier/index.ts

@@ -11,5 +11,6 @@ export default function ({ loadTestFile }: FtrProviderContext) {
    loadTestFile(require.resolve('./create_rules'));
    loadTestFile(require.resolve('./create_new_terms'));
    loadTestFile(require.resolve('./preview_rules'));
+    loadTestFile(require.resolve('./create_rules_bulk'));


This test file was not imported anywhere for some reason. Even though the tests in this file seem legit and not a duplicate of some other tests. So I imported it here.

…se-schedule-interval

nikitaindik · 2024-06-05T13:19:23Z

/ci

kibana-ci · 2024-06-05T14:54:55Z

💔 Build Failed

Failed CI Steps

Test Failures

[job] [logs] FTR Configs #99 / Monitoring Endpoints Elasticsearch "before all" hook in "Elasticsearch"
[job] [logs] FTR Configs #99 / Monitoring Endpoints Kibana Overview Package (metrics-*) should get kibana rules at cluster level
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions with frequencies it does not change actions frequency attributes when 'throttle' is 'undefined'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions with frequencies it does not change actions frequency attributes when 'throttle' is 'undefined'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 300s' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 300s' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 3h' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 3h' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 4d' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 4d' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 5m' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess @serverless @skipInServerlessMKI update_rules update rules per-action frequencies @skipInServerless actions without frequencies it correctly transforms 'throttle = 5m' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '10h'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '10h'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '2d'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '2d'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '321s'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '321s'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '6m'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is '6m'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'no_actions'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'no_actions'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'rule'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'rule'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'undefined'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions with frequencies it does not change actions frequency attributes when 'throttle' is 'undefined'
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 300s' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 300s' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 3h' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 3h' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 4d' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 4d' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 5m' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies actions without frequencies it correctly transforms 'throttle = 5m' and sets it as a frequency of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 1h' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 1h' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 430s' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 430s' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 7m' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 7m' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 8d' and overrides frequency attribute of each action
[job] [logs] FTR Configs #53 / Rules Management - Rule Update APIs @ess update_rules_bulk bulk per-action frequencies some actions with frequencies it correctly transforms 'throttle = 8d' and overrides frequency attribute of each action

Metrics [docs]

✅ unchanged

History

💔 Build #213920 failed d9f3079
💚 Build #213877 succeeded 557e61d
💚 Build #212818 succeeded 00e53e5
💔 Build #212807 failed 4890b53
💚 Build #212728 succeeded d766bf2

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

cc @nikitaindik @VidhiRambhia

VidhiRambhia and others added 3 commits November 22, 2023 19:39

Update PULL_REQUEST_TEMPLATE.md

f6babd2

Security Solution | Updating minimumScheduleInterval for cypress to 2…

d914b2a

…4 hours

Revert : Update PULL_REQUEST_TEMPLATE.md

e48ef62

VidhiRambhia mentioned this pull request Nov 23, 2023

[Security Solution] Fix flaky tests: common tasks #161505

Open

Merge branch 'main' into main

5e03410

VidhiRambhia marked this pull request as ready for review November 29, 2023 20:16

VidhiRambhia requested a review from a team as a code owner November 29, 2023 20:16

Merge branch 'main' into increase-schedule-interval

9c16065

kibanamachine added the 💝community label Nov 29, 2023

VidhiRambhia added 3 commits November 29, 2023 14:17

Merge branch 'main' into main

8e96abf

Merge branch 'main' into main

2020da4

Merge branch 'main' into increase-schedule-interval

99833e8

banderror reviewed Nov 30, 2023

View reviewed changes

x-pack/test/security_solution_cypress/config.ts Outdated Show resolved Hide resolved

banderror changed the title ~~Security Solution | Setting a large default rule interval~~ [Security Solution] Setting a large default rule interval Nov 30, 2023

banderror assigned VidhiRambhia Nov 30, 2023

VidhiRambhia added 4 commits November 30, 2023 23:50

Security Solution | Updating minimumScheduleInterval for cypress to 2…

61a5e17

…4 hours

Merge remote-tracking branch 'origin/main'

3fb0de8

Security Solution | Updating minimumScheduleInterval for cypress to 2…

c925a7b

…4 hours

Merge remote-tracking branch 'origin/increase-schedule-interval'

95c6479

VidhiRambhia requested review from a team as code owners December 1, 2023 19:02

PhilippeOberti approved these changes May 31, 2024

View reviewed changes

dhurley14 approved these changes May 31, 2024

View reviewed changes

nikitaindik added 2 commits June 3, 2024 15:20

Merge remote-tracking branch 'upstream/main' into VidhiRambhia_increa…

0494a85

…se-schedule-interval

Add a test to check default interval value if "interval" is not provided

4e88e0f

nikitaindik requested a review from dplumlee June 3, 2024 13:59

MadameSheema approved these changes Jun 3, 2024

View reviewed changes

dplumlee approved these changes Jun 3, 2024

View reviewed changes

Merge remote-tracking branch 'upstream/main' into VidhiRambhia_increa…

520842d

…se-schedule-interval

Merge branch 'main' into increase-schedule-interval

557e61d

nikitaindik added 2 commits June 4, 2024 16:15

Set interval to 24h for read rules tests

781c60c

Merge branch 'increase-schedule-interval' of github.com:VidhiRambhia/…

4948132

…kibana into VidhiRambhia_increase-schedule-interval

banderror reviewed Jun 4, 2024

View reviewed changes

Merge branch 'main' into increase-schedule-interval

d9f3079

nikitaindik added 3 commits June 5, 2024 10:02

Merge remote-tracking branch 'upstream/main' into VidhiRambhia_increa…

9905d2e

…se-schedule-interval

Update interval to 24h in getCreateThreatMatchRulesSchemaMock and…

adc38c6

… `getUpdateNewTermsSchemaMock`

Merge branch 'increase-schedule-interval' of github.com:VidhiRambhia/…

3e49539

…kibana into VidhiRambhia_increase-schedule-interval

nikitaindik marked this pull request as draft June 5, 2024 08:26

nikitaindik reviewed Jun 5, 2024

View reviewed changes

nikitaindik added 3 commits June 5, 2024 15:16

Update from in accordance with interval

fd3538b

Temporarily let CI run all API integration tests

e52d5a5

Merge remote-tracking branch 'upstream/main' into VidhiRambhia_increa…

ed0944d

…se-schedule-interval

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Security Solution] Setting a large default rule interval #171814

[Security Solution] Setting a large default rule interval #171814

VidhiRambhia commented Nov 23, 2023 •

edited by banderror

VidhiRambhia commented Nov 30, 2023

banderror left a comment

elasticmachine commented Nov 30, 2023

elasticmachine commented Nov 30, 2023

nikitaindik commented May 29, 2024

PhilippeOberti left a comment

dhurley14 left a comment

dhurley14 May 31, 2024

nikitaindik Jun 3, 2024 •

edited

nikitaindik commented Jun 3, 2024

MadameSheema left a comment

dplumlee left a comment

dplumlee Jun 3, 2024

nikitaindik Jun 4, 2024

banderror commented Jun 4, 2024

banderror commented Jun 4, 2024

banderror commented Jun 4, 2024

banderror Jun 4, 2024

nikitaindik Jun 5, 2024

banderror Jun 4, 2024

nikitaindik Jun 5, 2024

banderror Jun 4, 2024

banderror Jun 4, 2024

mistic commented Jun 4, 2024

nikitaindik commented Jun 5, 2024

nikitaindik Jun 5, 2024

nikitaindik commented Jun 5, 2024

kibana-ci commented Jun 5, 2024 •

edited

[Security Solution] Setting a large default rule interval #171814

Are you sure you want to change the base?

[Security Solution] Setting a large default rule interval #171814

Conversation

VidhiRambhia commented Nov 23, 2023 • edited by banderror

Summary

VidhiRambhia commented Nov 30, 2023

banderror left a comment

Choose a reason for hiding this comment

elasticmachine commented Nov 30, 2023

elasticmachine commented Nov 30, 2023

nikitaindik commented May 29, 2024

PhilippeOberti left a comment

Choose a reason for hiding this comment

dhurley14 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nikitaindik Jun 3, 2024 • edited

Choose a reason for hiding this comment

nikitaindik commented Jun 3, 2024

MadameSheema left a comment

Choose a reason for hiding this comment

dplumlee left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

banderror commented Jun 4, 2024

banderror commented Jun 4, 2024

banderror commented Jun 4, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mistic commented Jun 4, 2024

nikitaindik commented Jun 5, 2024

Choose a reason for hiding this comment

nikitaindik commented Jun 5, 2024

kibana-ci commented Jun 5, 2024 • edited

💔 Build Failed

Failed CI Steps

Test Failures

Metrics [docs]

History

VidhiRambhia commented Nov 23, 2023 •

edited by banderror

nikitaindik Jun 3, 2024 •

edited

kibana-ci commented Jun 5, 2024 •

edited