[Cloud Security] Fix Journey Performance FTR for Compliance Dashboard Page

[Omolola-Akinleye]

Currently, PR fails because of Journey Performance Test error.

Journey[cloud_security_dashboard]
--
  | Go to cloud security dashboards Page:
  | Step [Go to cloud security dashboards Page] failed: page.waitForSelector: Timeout 30000ms exceeded.
  | =========================== logs ===========================
  | waiting for locator('[data-test-subj="csp:dashboard-sections-table-header-score"]') to be visible
  | ============================================================
  | page.waitForSelector: Timeout 30000ms exceeded.
  | =========================== logs ===========================
  | waiting for locator('[data-test-subj="csp:dashboard-sections-table-header-score"]') to be visible
  | ============================================================
  | at Object.fn (cloud_security_dashboard.ts:51:14)
  | at journey_ftr_harness.ts:432:15
  | at JourneyFtrHarness.withSpan (journey_ftr_harness.ts:281:14)
  | at Context.<anonymous> (journey_ftr_harness.ts:430:11)
  | at Object.apply (wrap_function.js:73:16)

We need to investigate how Performance journey FTRs run and debug why Dashboard test failure occurs.

To run the performance test cli to see test error node scripts/run_performance.js --journey-path x-pack/performance/journeys/cloud_security_dashboard.ts

DOD:

• Use es-archiver cli to save cspm data scripts/es_archiver.js save
• Update FTR config
• Fix Go Cloud Security Dashboard error
• Document Performance Testing process

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

[kfirpeled]

Closing as not planned. We covered this together and agreed that there's no issue with the test and it should work seamlessly with https://github.com/elastic/kibana/pull/173853 changes

[Omolola-Akinleye]

Hi @kfirpeled, The PR for dashboard tab doesn't cause the journey test issues. However, the test fails in main branch.

I believe there the test is failing because es_archiver.js doesn't have the support to create Cloud Security indices. A ticket was opened last week.