Open dmlemeshko opened 1 year ago
Pinging @elastic/kibana-qa (Team:QA)
Here are some ideas. A concurrency test is basically a proxy for how long a certain route blocks the event loop or to ensure we don't hit an OOM condition. To prevent an impact on Kibana availability we should avoid regressions in:
These suggestions are based on https://overview.elastic-cloud.com/app/dashboards#/view/91b76e00-7750-11ed-bdfe-fd5199a89568?_g=() because the request path in the proxy logs include the space and any uuid
s if applicable, it means this analysis excludes a lot of APIs but it's a start. Would be better to analyse APM traces as that would generalise any parameters in the request path.
Some based on personal experience in SDHs others based on the biggest request / response size * number of requests
. Many of these APIs depend on having the right "fixtures" in tests to be helpful.
/api/console/autocomplete_entities
(requires large field count across indices)/api/telemetry/v2/clusters/_stats
(large number of SOs, many visualisations, many data views, large field count)/api/index_patterns/_fields_for_wildcard
(large field count for a single data view)/api/saved_objects/_bulk_resolve
/internal/uptime/pings
/api/fleet/agents/:uuid/checkin
/api/apm/settings/agent-configuration/search
(there are plans to move away from/reduce the volume of calls to this API that might have been completed in recent releases so might not be necessary to test)/*/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js
/
/internal/bsearch
/login
/api/metrics/vis/data
/internal/security/session
/api/console/proxy
/api/saved_objects_tagging/tags
/api/ui_counters/_report
/api/status
Security
Core
Licensing
Saved objects
Telemetry
Misc