7405b93f18
* [ML] Async Search Service.
* [ML] Log Log Area Charts Grid. Scatterplot with streaming data.
* [ML] Remove scatterplot streaming demo.
* [ML] Improved histogram bins for log scale.
* [ML] Move client side code from Ml to APM plugin.
* [ML] Adds correlation table.
* [ML] Layout tweaks.
* [ML] Move server side code from ML to APM.
* [ML] Remove console.logs.
* [ML] Fix types.
* [ML] Chart area line type fix. Slowness %.
* [ML] Comment unused vars.
* Fix missing pluginsStart data in context
* Add KS test value and rename table columns
* Update percentiles to be correct
* Make columns optional
* Update fractionals/expectations to match with backend logic
* Update so progress is 100% when all is completed
* Make pre-processing steps smaller part of overall progress(to show charts earlier)
* Add no correlations found message
* Fix progress logic
* Fix incorrect threshold, types
* Add back APM filtering functionality to match with other table
* Improve histogram equality check with random sampling
* Show overall latency distribution right away
* Rename demo tab to latencyCorrelationsTab
* Update percentiles query to use hdr
* [ML] Fix issue where apm-* might have multiple indices with different mappings where keyword is not the only type
- Fix to check for keyword mapping more thoroughly
- Add try catch if one of the es search fail, don't quit the entire fetch
* Remove commented code
* Remove kstest column, round correlation to 2 sigfig dec
* Remove old latency tab, replace with ml latency correlations tab as first/default one
* Set axis to start at 0 because agg may results in weird
* Remove commented code for grouping duplicates
* Update msg to mean significant correlations
* Add i18n
* Change correlations flyout back to medium size
* Add name of service or transaction for clarity
* Share i18n
* Consolidate roundToDecimalPlace usage
* Remove redundant isDuplicate
* Create MAX_CORRELATIONS_TO_SHOW
* Update mlCorrelationcolumns
* Fix i18n quotations
* Update query to include filter
* Revert "Update query to include filter"
This reverts commit
|
||
|---|---|---|
| .. | ||
| build_chromium | ||
| dev-tools | ||
| examples | ||
| plugins | ||
| scripts | ||
| tasks | ||
| test | ||
| .gitignore | ||
| .i18nrc.json | ||
| .telemetryrc.json | ||
| gulpfile.js | ||
| package.json | ||
| README.md | ||
| yarn.lock | ||
Elastic License Functionality
This directory tree contains files subject to the Elastic License 2.0. The files subject to the Elastic License 2.0 are grouped in this directory to clearly separate them from files dual-licensed under the Server Side Public License and the Elastic License 2.0.
Development
By default, Kibana will run with X-Pack installed as mentioned in the contributing guide.
Elasticsearch will run with a basic license. To run with a trial license, including security, you can specifying that with the yarn es command.
Example: yarn es snapshot --license trial --password changeme
By default, this will also set the password for native realm accounts to the password provided (changeme by default). This includes that of the kibana_system user which elasticsearch.username defaults to in development. If you wish to specify a password for a given native realm account, you can do that like so: --password.kibana_system=notsecure
Testing
For information on testing, see the Elastic functional test development guide.
Running functional tests
The functional UI tests, the API integration tests, and the SAML API integration tests are all run against a live browser, Kibana, and Elasticsearch install. Each set of tests is specified with a unique config that describes how to start the Elasticsearch server, the Kibana server, and what tests to run against them. The sets of tests that exist today are functional UI tests (specified by this config), API integration tests (specified by this config), and SAML API integration tests (specified by this config).
The script runs all sets of tests sequentially like so:
- builds Elasticsearch and X-Pack
- runs Elasticsearch with X-Pack
- starts up the Kibana server with X-Pack
- runs the functional UI tests against those servers
- tears down the servers
- repeats the same process for the API and SAML API integration test configs.
To do all of this in a single command run:
node scripts/functional_tests
Developing functional UI tests
If you are developing functional tests then you probably don't want to rebuild Elasticsearch and wait for all that setup on every test run, so instead use this command to build and start just the Elasticsearch and Kibana servers:
node scripts/functional_tests_server
After the servers are started, open a new terminal and run this command to run just the tests (without tearing down Elasticsearch or Kibana):
node scripts/functional_test_runner
For both of the above commands, it's crucial that you pass in --config to specify the same config file to both commands. This makes sure that the right tests will run against the right servers. Typically a set of tests and server configuration go together.
Read more about how the scripts work here.
For a deeper dive, read more about the way functional tests and servers work here.
Running API integration tests
API integration tests are run with a unique setup usually without UI assets built for the Kibana server.
API integration tests are intended to test only programmatic API exposed by Kibana. There is no need to run browser and simulate user actions, which significantly reduces execution time. In addition, the configuration for API integration tests typically sets optimize.enabled=false for Kibana because UI assets are usually not needed for these tests.
To run only the API integration tests:
node scripts/functional_tests --config test/api_integration/config
Running SAML API integration tests
We also have SAML API integration tests which set up Elasticsearch and Kibana with SAML support. Run only API integration tests with SAML enabled like so:
node scripts/functional_tests --config test/security_api_integration/saml.config
Running Jest integration tests
Jest integration tests can be used to test behavior with Elasticsearch and the Kibana server.
yarn test:jest_integration
Running Reporting functional tests
See here for more information on running reporting tests.
Running Security Solution Cypress E2E/integration tests
See here for information on running this test suite.