Skip to content

Commit fc2ecd1

Browse files
authored
[ML] Log Rate Analysis: Fix Performance journey test (elastic#244871)
Resolves elastic#244725 The dataset used for testing produces a spike change point, however, it wasn't detected previously due to the elastic/elasticsearch#127517 issue. That issue was fixed in elastic/elasticsearch@352229b, and after the fix, our test no longer matched the newly produced change point. In this PR, we update the assertions to expect the spike and run the analysis against it.
1 parent 6886329 commit fc2ecd1

2 files changed

Lines changed: 7 additions & 11 deletions

File tree

.buildkite/ftr_platform_stateful_configs.yml

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,9 +50,6 @@ disabled:
5050
- x-pack/platform/test/functional_gen_ai/inference/config.ts
5151
- x-pack/platform/test/onechat/smoke_tests/config.stateful.ts
5252

53-
# Temporary skip while investigating failures
54-
- x-pack/performance/journeys_e2e/aiops_log_rate_analysis.ts
55-
5653
defaultQueue: 'n2-4-spot'
5754
enabled:
5855
- src/platform/test/accessibility/config.ts
@@ -346,6 +343,7 @@ enabled:
346343
- x-pack/platform/test/upgrade_assistant_integration/config.ts
347344
- x-pack/platform/test/reindex_service/config.ts
348345
- x-pack/platform/test/usage_collection/config.ts
346+
- x-pack/performance/journeys_e2e/aiops_log_rate_analysis.ts
349347
- x-pack/performance/journeys_e2e/ecommerce_dashboard.ts
350348
- x-pack/performance/journeys_e2e/ecommerce_dashboard_http2.ts
351349
- x-pack/performance/journeys_e2e/ecommerce_dashboard_map_only.ts

x-pack/performance/journeys_e2e/aiops_log_rate_analysis.ts

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -30,16 +30,14 @@ export const journey = new Journey({
3030
parentLocator: subj('aiopsDocumentCountChart'),
3131
count: 1,
3232
});
33-
await page.waitForSelector(subj('aiopsNoWindowParametersEmptyPrompt'));
33+
// Wait for the change point detection to complete and show the spike detected prompt.
34+
// The test data has all documents at a single timestamp, creating a clear spike pattern.
35+
await page.waitForSelector(subj('aiopsChangePointDetectedPrompt'));
3436
})
3537
.step('Run AIOps Log Rate Analysis', async ({ page }) => {
36-
// Select the chart and click in the area where the spike is located.
37-
const chart = await page.locator(subj('aiopsDocumentCountChart'));
38-
await chart.click({ position: { x: 710, y: 50 } });
39-
40-
// Click the "Run analysis" button.
41-
await page.waitForSelector(subj('aiopsLogRateAnalysisNoAutoRunContentRunAnalysisButton'));
42-
await page.click(subj('aiopsLogRateAnalysisNoAutoRunContentRunAnalysisButton'));
38+
// Click the "Run analysis" button to analyze the detected spike.
39+
await page.waitForSelector(subj('aiopsLogRateAnalysisContentRunAnalysisButton'));
40+
await page.click(subj('aiopsLogRateAnalysisContentRunAnalysisButton'));
4341

4442
// Wait for the analysis to complete.
4543
await page.waitForSelector(subj('aiopsAnalysisComplete'), { timeout: 120000 });

0 commit comments

Comments
 (0)