[Security Solution] Enable debug logging for Rule Management integration tests#229185
Merged
nikitaindik merged 26 commits intoelastic:mainfrom Aug 1, 2025
Merged
[Security Solution] Enable debug logging for Rule Management integration tests#229185nikitaindik merged 26 commits intoelastic:mainfrom
nikitaindik merged 26 commits intoelastic:mainfrom
Conversation
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8805[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 200/200 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8822[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 25/25 tests passed. |
nikitaindik
force-pushed
the
flaky-test-investigation
branch
from
ad37c0a to
56121d6
Compare
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8825[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 100/100 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8830[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 100/100 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8834[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 200/200 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8847[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 200/200 tests passed. |
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8850[❌] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 0/25 tests passed. |
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8855[❌] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 0/25 tests passed. |
…Reporter overrides
Contributor
Flaky Test Runner Stats🟠 Some tests failed. - kibana-flaky-test-suite-runner#8857[❌] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 0/25 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8859[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 100/100 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8864[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 100/100 tests passed. |
Contributor
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8888[✅] x-pack/test/security_solution_api_integration/test_suites/detections_response/rules_management/rule_import_export/trial_license_complete_tier/configs/ess.config.ts: 100/100 tests passed. |
Contributor
Author
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
nikitaindik
added a commit
to nikitaindik/kibana
that referenced
this pull request
Aug 1, 2025
…ion tests (elastic#229185) **Partially addresses: elastic#229688 ## Summary This PR enables debug logging for all API integration tests owned by the Rules Management team. Our team has seen a spike in flaky tests recently. To be able to quickly debug such situations, we want to add debug logging. The logging itself will be added in a follow-up PR. This PR only enables it for all our tests. ## Changes - Added 4 new FTR base configs: - 2 for ESS: `rules_management.basic.config.ts` and `rules_management.trial.config.ts` - 2 for Serverless: `rules_management.essentials.config.ts` and `rules_management.complete.config.ts` - These new FTR configs extend existing base configs to enable logging for `securitySolution` and `fleet` plugins on `debug` level. - Updated existing test configs to use the new base configs. Now, debug logs from test suites and the Kibana backend will be visible in BuildKite reports when clicking the "[logs]" button. <img width="573" height="118" alt="logs_button" src="https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74" />⚠️ Please note that debug logs will not appear in the "FTR Configs #<number>" collapsible sections in BuildKite. They will only be available in "[logs]" reports for **failed** tests.
nikitaindik
added a commit
that referenced
this pull request
Aug 1, 2025
…ntegration tests (#229185) (#230248) # Backport This will backport the following commits from `main` to `8.19`: - [[Security Solution] Enable debug logging for Rule Management integration tests (#229185)](#229185) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-08-01T08:13:06Z","message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","v9.2.0","v9.0.5","v9.1.1","v8.18.5","v8.19.1"],"title":"[Security Solution] Enable debug logging for Rule Management integration tests","number":229185,"url":"https://github.com/elastic/kibana/pull/229185","mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/229185","number":229185,"mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
nikitaindik
added a commit
that referenced
this pull request
Aug 1, 2025
…tegration tests (#229185) (#230246) # Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Enable debug logging for Rule Management integration tests (#229185)](#229185) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-08-01T08:13:06Z","message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","v9.2.0","v9.0.5","v9.1.1","v8.18.5","v8.19.1"],"title":"[Security Solution] Enable debug logging for Rule Management integration tests","number":229185,"url":"https://github.com/elastic/kibana/pull/229185","mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/229185","number":229185,"mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
nikitaindik
added a commit
that referenced
this pull request
Aug 1, 2025
…ntegration tests (#229185) (#230249) # Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Enable debug logging for Rule Management integration tests (#229185)](#229185) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-08-01T08:13:06Z","message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","v9.2.0","v9.0.5","v9.1.1","v8.18.5","v8.19.1"],"title":"[Security Solution] Enable debug logging for Rule Management integration tests","number":229185,"url":"https://github.com/elastic/kibana/pull/229185","mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/229185","number":229185,"mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
This was referenced Aug 4, 2025
szaffarano
pushed a commit
to szaffarano/kibana
that referenced
this pull request
Aug 5, 2025
…ion tests (elastic#229185) **Partially addresses: elastic#229688 ## Summary This PR enables debug logging for all API integration tests owned by the Rules Management team. Our team has seen a spike in flaky tests recently. To be able to quickly debug such situations, we want to add debug logging. The logging itself will be added in a follow-up PR. This PR only enables it for all our tests. ## Changes - Added 4 new FTR base configs: - 2 for ESS: `rules_management.basic.config.ts` and `rules_management.trial.config.ts` - 2 for Serverless: `rules_management.essentials.config.ts` and `rules_management.complete.config.ts` - These new FTR configs extend existing base configs to enable logging for `securitySolution` and `fleet` plugins on `debug` level. - Updated existing test configs to use the new base configs. Now, debug logs from test suites and the Kibana backend will be visible in BuildKite reports when clicking the "[logs]" button. <img width="573" height="118" alt="logs_button" src="https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74" />⚠️ Please note that debug logs will not appear in the "FTR Configs #<number>" collapsible sections in BuildKite. They will only be available in "[logs]" reports for **failed** tests.
kibanamachine
added
the
backport missing
Contributor
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
nikitaindik
added a commit
that referenced
this pull request
Aug 5, 2025
…tegration tests (#229185) (#230242) # Backport This will backport the following commits from `main` to `9.1`: - [[Security Solution] Enable debug logging for Rule Management integration tests (#229185)](#229185) <!--- Backport version: 10.0.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-08-01T08:13:06Z","message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","backport:version","v9.2.0","v9.0.5","v9.1.1","v8.18.5","v8.19.1"],"title":"[Security Solution] Enable debug logging for Rule Management integration tests","number":229185,"url":"https://github.com/elastic/kibana/pull/229185","mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","9.1","8.18","8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/229185","number":229185,"mergeCommit":{"message":"[Security Solution] Enable debug logging for Rule Management integration tests (#229185)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/229688**\n\n## Summary\nThis PR enables debug logging for all API integration tests owned by the\nRules Management team.\n\nOur team has seen a spike in flaky tests recently. To be able to quickly\ndebug such situations, we want to add debug logging. The logging itself\nwill be added in a follow-up PR. This PR only enables it for all our\ntests.\n\n## Changes\n- Added 4 new FTR base configs:\n- 2 for ESS: `rules_management.basic.config.ts` and\n`rules_management.trial.config.ts`\n- 2 for Serverless: `rules_management.essentials.config.ts` and\n`rules_management.complete.config.ts`\n- These new FTR configs extend existing base configs to enable logging\nfor `securitySolution` and `fleet` plugins on `debug` level.\n- Updated existing test configs to use the new base configs.\n\nNow, debug logs from test suites and the Kibana backend will be visible\nin BuildKite reports when clicking the \"[logs]\" button.\n\n<img width=\"573\" height=\"118\" alt=\"logs_button\"\nsrc=\"https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74\"\n/>\n\n⚠️ Please note that debug logs will not appear in the \"FTR Configs\n#<number>\" collapsible sections in BuildKite. They will only be\navailable in \"[logs]\" reports for **failed** tests.","sha":"063d94a2e30b615174acd84cfafdd24cef71dece"}},{"branch":"9.0","label":"v9.0.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->
kibanamachine
removed
the
backport missing
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 5, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> (cherry picked from commit 2d4e421)
nikitaindik
added a commit
to nikitaindik/kibana
that referenced
this pull request
Aug 5, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
nikitaindik
added a commit
to nikitaindik/kibana
that referenced
this pull request
Aug 5, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> (cherry picked from commit 2d4e421) # Conflicts: # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/bootstrap_prebuilt_rules/bootstrap_prebuilt_rules_handler.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/install_prebuilt_rules_and_timelines/install_prebuilt_rules_and_timelines_route.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/install_prebuilt_rules_and_timelines/legacy_create_prepackaged_rules.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/perform_rule_installation/perform_rule_installation_handler.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/register_routes.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/ensure_latest_rules_package_installed.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/find_latest_package_version.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_ai_prompts.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_endpoint_package.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_prebuilt_rules_package.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_promotion_rules.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/rules_package/install_endpoint_security_prebuilt_rule.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/routes/__mocks__/request_context.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/rule_management/logic/import/rule_source_importer/rule_source_importer.ts
nikitaindik
added a commit
to nikitaindik/kibana
that referenced
this pull request
Aug 5, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> (cherry picked from commit 2d4e421) # Conflicts: # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/bootstrap_prebuilt_rules/bootstrap_prebuilt_rules_handler.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/install_prebuilt_rules_and_timelines/install_prebuilt_rules_and_timelines_route.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/install_prebuilt_rules_and_timelines/legacy_create_prepackaged_rules.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/perform_rule_installation/perform_rule_installation_handler.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/api/register_routes.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/ensure_latest_rules_package_installed.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/find_latest_package_version.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_ai_prompts.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_endpoint_package.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_prebuilt_rules_package.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/integrations/install_promotion_rules.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/prebuilt_rules/logic/rules_package/install_endpoint_security_prebuilt_rule.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/routes/__mocks__/request_context.ts # x-pack/solutions/security/plugins/security_solution/server/lib/detection_engine/rule_management/logic/import/rule_source_importer/rule_source_importer.ts
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
…ion tests (elastic#229185) **Partially addresses: elastic#229688 ## Summary This PR enables debug logging for all API integration tests owned by the Rules Management team. Our team has seen a spike in flaky tests recently. To be able to quickly debug such situations, we want to add debug logging. The logging itself will be added in a follow-up PR. This PR only enables it for all our tests. ## Changes - Added 4 new FTR base configs: - 2 for ESS: `rules_management.basic.config.ts` and `rules_management.trial.config.ts` - 2 for Serverless: `rules_management.essentials.config.ts` and `rules_management.complete.config.ts` - These new FTR configs extend existing base configs to enable logging for `securitySolution` and `fleet` plugins on `debug` level. - Updated existing test configs to use the new base configs. Now, debug logs from test suites and the Kibana backend will be visible in BuildKite reports when clicking the "[logs]" button. <img width="573" height="118" alt="logs_button" src="https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74" />⚠️ Please note that debug logs will not appear in the "FTR Configs #<number>" collapsible sections in BuildKite. They will only be available in "[logs]" reports for **failed** tests.
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
…ion tests (elastic#229185) **Partially addresses: elastic#229688 ## Summary This PR enables debug logging for all API integration tests owned by the Rules Management team. Our team has seen a spike in flaky tests recently. To be able to quickly debug such situations, we want to add debug logging. The logging itself will be added in a follow-up PR. This PR only enables it for all our tests. ## Changes - Added 4 new FTR base configs: - 2 for ESS: `rules_management.basic.config.ts` and `rules_management.trial.config.ts` - 2 for Serverless: `rules_management.essentials.config.ts` and `rules_management.complete.config.ts` - These new FTR configs extend existing base configs to enable logging for `securitySolution` and `fleet` plugins on `debug` level. - Updated existing test configs to use the new base configs. Now, debug logs from test suites and the Kibana backend will be visible in BuildKite reports when clicking the "[logs]" button. <img width="573" height="118" alt="logs_button" src="https://github.com/user-attachments/assets/eb7de404-d6b9-4402-993d-0b8320ec0e74" />⚠️ Please note that debug logs will not appear in the "FTR Configs #<number>" collapsible sections in BuildKite. They will only be available in "[logs]" reports for **failed** tests.
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
**Partially addresses: elastic#229688 **Is a follow-up to: elastic#229185 ## Summary This PR adds debug logging to the areas where the Rule Management backend interacts with Fleet APIs. This is to help us troubleshoot flaky tests. --------- Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>
This was referenced Sep 5, 2025
Open
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
Partially addresses: #229688
Summary
This PR enables debug logging for all API integration tests owned by the Rules Management team.
Our team has seen a spike in flaky tests recently. To be able to quickly debug such situations, we want to add debug logging. The logging itself will be added in a follow-up PR. This PR only enables it for all our tests.
Changes
rules_management.basic.config.tsandrules_management.trial.config.tsrules_management.essentials.config.tsandrules_management.complete.config.tssecuritySolutionandfleetplugins ondebuglevel.Now, debug logs from test suites and the Kibana backend will be visible in BuildKite reports when clicking the "[logs]" button.