* Fix buildEsQuery to ignore filters if not in index (#29880)
* Fix buildEsQuery to ignore filters if not in index
* Fix tests and move getEsQueryConfig to package
* Revert changes to TSVB
* Remove console log
* Review feedback
* Fix tests
* Use 's' instead of 'm' to match newlines instead of doing multi-line
* Fix autocomplete suggestions to handle newlines and tabs in field names
* Add line feed to escaped whitespace
* Refactor snapshot histogram ES query and subsequent processing.
* Fix issues on client, remove obsolete code, update tests.
* Get type check passing and update Snapshot component's unit tests to work with new schema data.
* Perf: avoid matrix transpose in canvas layout that served only initial docu purpose, don't cons extra arrays
* Chore: switch to ES2015 import/export and direct function access
* Chore: TS conversion for some of the layout engine files
* Chore: rework TS linting for all files under `aeroelastic` (even the `.js` ones)
* Handle warnings from task manager without stack traces.
* Fix typescript errors.
* Catch no living connection errors.
Swallow stack traces and do not throw errors.
* Should use string substitution instead of concatenation.
A content security policy is a great addition to the protections built
into Kibana, but it's not effective in older browsers (like IE11) that
do not enforce the policy.
When CSP strict mode is enabled, right before the Kibana app is
bootstrapped, a basic safety check is performed to see if "naked" inline
scripts are rejected. If inline scripting is allowed by the browser,
then an error message is presented to the user and Kibana never attempts
to bootstrap.
* csp: nonce and unsafe-eval for scripts
To kick things off, a rudimentary CSP implementation only allows
dynamically loading new JavaScript if it includes an associated nonce
that is generated on every load of the app.
A more sophisticated content security policy is necessary, particularly
one that bans eval for scripts, but one step at a time.
* img-src is not necessary if the goal is not to restrict
* configurable CSP owned by security team
* smoke test
* remove x-content-security-policy
* document csp.rules
* fix tsconfig for test
* switch integration test back to regular js
* stop looking for tsconfig in test
* grrr, linting errors not caught by precommit
* docs: people -> you for consistency sake
Co-Authored-By: epixa <court@epixa.com>
* [Uptime] Remove pointless max search size box (#29992)
This box is just confusing. You can only see 100 results so we should just hard-code that. Having it is left-over from a previous design.
* Update snap
