github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-22 17:04:01 -04:00
Code Issues Projects Releases Packages Wiki Activity
kibana/x-pack/test/scalability
History
Exact
Dzmitry Lemechko aa1037f958
[scalability testing] get the correct Gatling report (#153089) 
## Summary

Adjusting the logic to pick the correct Gatling report after run:

It turns out `startWith` was picking the wrong report since 2 api
journey names match the pattern:


`api.telemetry.cluster_stats.no_cache.json`
`api.telemetry.cluster_stats.no_cache.1600_dataviews.json`

This PR fixes the issue, so that we report to Telemetry stats for the
correct journey.

Testing here
https://buildkite.com/elastic/kibana-apis-capacity-testing/builds/450

---------

Co-authored-by: Tre' <wayne.seymour@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-03-10 13:55:34 +01:00
..
apis [Telemetry] Add scalability tests for known bottlenecks (#151110) 2023-03-10 10:45:36 +01:00
fixtures/kbn_archiver [Telemetry] Add scalability tests for known bottlenecks (#151110) 2023-03-10 10:45:36 +01:00
config.ts [performance] use journey own ftr config to run scalability test (#152596) 2023-03-07 13:20:21 +01:00
disabled_scalability_tests.json [scalability testing] add json to track skipped journeys (#151629) 2023-02-21 17:58:50 +01:00
events_shipper.ts Benchmark single apis (#146297) 2023-01-09 16:38:30 +01:00
ftr_provider_context.ts [ftr] add first-class support for playwrite journeys (#140680) 2022-09-22 01:06:46 -07:00
report_parser.ts Benchmark single apis (#146297) 2023-01-09 16:38:30 +01:00
runner.ts [scalability testing] get the correct Gatling report (#153089) 2023-03-10 13:55:34 +01:00
types.ts [performance] use journey own ftr config to run scalability test (#152596) 2023-03-07 13:20:21 +01:00