kibana/x-pack/plugins/searchprofiler
Mikhail Shustov b6e582c53e
TS Incremental build exclude test files (#95610)
* add base config for all the TS projects

* all the project use new tsconfig.project.json

* compile test files in the high-level tsconfig.json

* fix TS error in maps plugin

* fix TS error in infra plugin

* exclude mote test and test until folders

* uptime. do not import test code within prod code

* expressions. do not import test code within prod code

* data: export mocks from high level folder

* task_manager: comply with es client typings

* infra: remove unused enzyme_helpers

* check_ts_project requires "include" key

* ts_check should handle parent configs

* all ts configs should extend base one

* exclude test folders from plugins

* update patterns to fix ts_check errors

* Apply suggestions from code review

Co-authored-by: Constance <constancecchen@users.noreply.github.com>

* uptime: MountWithReduxProvider to test helpers

Co-authored-by: Constance <constancecchen@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2021-04-01 14:40:47 +02:00
..
common Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
public Implement custom global header banner (#87438) 2021-02-11 10:12:24 +01:00
server ES client : use the new type definitions (#83808) 2021-03-25 04:47:16 -04:00
jest.config.js Elastic License 2.0 (#90099) 2021-02-03 18:12:39 -08:00
kibana.json [DX] move some ES UI plugins to TS project (#88050) 2021-01-13 21:58:34 +01:00
README.md Conform Search Profiler application organization to other ES UI plugins (#82085) 2020-11-02 12:01:27 -08:00
tsconfig.json TS Incremental build exclude test files (#95610) 2021-04-01 14:40:47 +02:00

Search Profiler

About

The search profiler consumes the Profile API by sending a search API with profile: true enabled in the request body. The response contains detailed information on how Elasticsearch executed the search request. People use this information to understand why a search request might be slow.

How to test

Query profile

Execute the default query to generate results in the Query profile tab.

{
  "query":{
    "match_all" : {}
  }
}

Aggregation profile

Execute an aggregation query to generate results in the Aggregation profile tab.

{
  "aggs": {
    "avg_grade": { "avg": { "field": "grade" } }
  }
}