Open afharo opened 1 year ago
Pinging @elastic/kibana-core (Team:Core)
(probably something I should know, but!) How / where should those scalability test added, exactly?
@pgayvallet Sorry! I forgot to add the link to the relevant area of the code: https://github.com/elastic/kibana/tree/main/x-pack/test/scalability/apis
We may want to add:
GET /translations/{locale}.json
GET /api/kibana/settings
Now regarding savedObjects... We're directly dependant on ES performances and ES-Kib connectivity here, but we're still doing additional work, so it could make sense to add scalability tests for the base APIs, e.g
GET /api/saved_objects/{type}/{id}
POST /api/saved_objects/{type}/{id}
PUT /api/saved_objects/{type}/{id}
(this one may be tricky because of concurrency / conflicts, not sure we can do it with the current system)WDYT?
We should aim for 100% coverage in Scalability tests on Core's public APIs.
This will help us understand where our bottlenecks are and make better-informed decisions on performance improvements.
Let's list here the most important APIs so we can start with something:
GET /api/status
#164864GET /index.html
GET /bootstrap.js