* Leading/trailing control columns first pass
* Add leading and trailing action column tests
* Remove unused prop type
* Use control column array constants
## Summary
Phase 1 of a multi-phase cautious approach for adding an experimental application cache for Kibana solutions called `metric_entities` and integrates it within Security Solutions.
Phase 1 is putting experimental support into the application without breaking existing features. Lots of TODO's, conversations and a possible RFC from phase 1 to phase 2 approach. Some features are missing, but for phase 1 the general idea and code is all there.
To enable this first phase after checking out the branch add this to your `kibana.dev.yml`
```yml
xpack.metricsEntities.enabled: true
xpack.securitySolution.enableExperimental: ['metricsEntitiesEnabled']
```
Then go into Stack Management -> Advanced Settings (Under Security Solutions) and set the enabled to true like so:
<img width="1229" alt="Screen Shot 2021-04-08 at 2 21 02 PM" src="https://user-images.githubusercontent.com/1151048/114091276-b3cbb700-9875-11eb-9083-5c1d91dd20ed.png">
Next go to the security_solutions page and you will see it being activated and you will have these transforms running if you look under stack management:
<img width="1710" alt="Screen Shot 2021-04-29 at 2 00 27 PM" src="https://user-images.githubusercontent.com/1151048/116611174-4a2e4e00-a8f3-11eb-9e15-55cb504dfb2a.png">
On the hosts page, network, page, etc... You can see them being activated when you have no query/filter and you click on request:
<img width="1405" alt="Screen Shot 2021-04-29 at 2 01 28 PM" src="https://user-images.githubusercontent.com/1151048/116611274-6a5e0d00-a8f3-11eb-9998-9f5b3d1c5c63.png">
You will see in the request the index patterns all starting with `estc_xyz*`
### Checklist
Delete any items that are not applicable to this PR.
- [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/master/packages/kbn-i18n/README.md)
We have lots of TODO's but no concrete docs with this just yet.
- [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials
Behind a feature flag and this isn't there yet.
- [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
* Set up basic Schema skeleton views+router
* Update engine router + nav with new schema routes
* Breadcrumbs
* PR feedback: derpin
Co-authored-by: Jason Stoltzfus <jastoltz24@gmail.com>
* reindexJobId pls
* my life is in shambles
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Jason Stoltzfus <jastoltz24@gmail.com>
* Move schema-specific shared types to shared/schema folder
- This helps provide more context when people are reaching into shared types grab items, and keeps concepts/components together
+ minor comment updates
* Convert interfaces to Records where applicable
- see https://www.typescriptlang.org/docs/handbook/utility-types.html#recordkeystype
* [Opinionated] Change schema types to enums and DRY out field_types constants
- in favor of using SchemaType enum keys and iterating
- Not 100% sure about this as the internet seems to think string unions are still pretty good, but since we're using const references for the types anyway, it seems like the use case fits
* Update files to use new schema type enum
* Update all remaining files (basic imports)
* [Misc] DRY out FieldCoercionErrors type
+ change to record
- AS will also use this type
* Pie: Field names are not escaped in expression
* Add a test case for single and double quotes to pie_fn.test
* Revert pie_fn and its test, remove escaping for vis config
* Update to_ast_pie
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
- Fixes correctly escaping the characters .[] in field names with double backslashes since Vega treats dots/brackets in field names special to be able to access attributes in object structures. This replaces the old approach that replaced dots with a similar but different UTF-8 character but missed the brackets.
- Additionally adds an EuiErrorBoundary component around the VegaChart component so we don't crash the whole page should another issue with Vega bubble up.
* convert functional_tests/lib into TS
* convert ES cluster factory into TS
* fix exports from kbn-test
* fix core test_helpers
* remove legacy ES client usage in ui_settings tests
* remove unnecessary ts-expect-errors comments
* initialize DEFAULT_SETTINGS_WITH_CORE_PLUGINS lazily to prevent failure when imported outside of FTR context
* throw an exception on invalid process.env.TEST_ES_PORT
* [TSVB] Timeseries Drop last bucket should default to false
* Rename isLastBucketDropped prop and move series domain calculation to a separate file
* Fix failing tests because of wrong default value
* update drop_last_bucket.js
* Refactor drop_last_bucket and some functional tests
* Change infra metrics test values because of last bucket value changed
* Refactor series_domain_calculation and related code
* Update series_domain_calculations.test
* Update series_domain_calculations.test
* Fix tooltip showing wrong time
* Refactor index
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
* initial migration away from ILegacyScopedClusterClient to
IScopedClusterClient and from "isEsError" to "handleEsError"
* re-instate ignore: [404]
* remove use of ignore_unavailable
* get the correct payload from the response
* fix use of new licensePreRoutingFactory
* fix jest tests
* address CJs feedback and re-add ignore_unavailable, clean up remaining TODOs
* remove legacy client config
* undo renaming as part of destructuring assignment
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Retrieve rules to export with a single query, greatly improving export performance
* Chunk rule IDs so exporting more than 1024 rules works
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Add SynonymsLogic create/update/delete actions & modal state
* [Setup] Update MultiInputRows to work with a ModalFooter submit + allow hiding submit button
* Add SynonymModal component
* Update existing views with modal behavior
* PR feedback: Fix MultiInputRows to not render a form component for Relevance Tuning / onChange-only components
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Add essql search strategy, new escount temporary function, and new essql temporary function
* Move old es* functions to legacy, add esdocs to use search strategy, add parameter arg for essql
* Clean up
* cleanup
* cleanup
* Move request builder files to common
* cleanup
* add comment
* PR Feedback
* Removing old types
* update type
* Add data.search to labs and fix error messages
* Fix function help type
* Add data service to usage collector types
* Update telemetry
* remove unrelated telemetry change
* Enable multi value leniency for SQL queries
* Display data service lab project
## [Security Solution][Timeline] Fixes an issue where many `OR` clauses take up too much vertical space
This PR makes Timeline's drag and drop query area resizable and scrollable to fix an issue reported by @aarju, where many `OR` clauses take up too much vertical space in Timeline.
To fix this issue:
* Timeline's drop area is now resizable
* The drop area still grows vertically, up to one third the size of the view hight
* A vertical scroll bar will automatically be displayed when entire query doesn't fit vertically within the drop area
The fix is shown in the animated gif below:
_Above: Timeline's drop area is now resizable and scrollable_
### Side-by-side comparison
The side-by-side browsers in the image below show the same timeline in full screen mode before the fix (on the left), and after the fix (on the right):
_Above: Timeline in full screen mode before the fix (left), and after the fix (right)_
### Steps to reproduce
1. Create a new timeline
2. Drag approximately 15 fields as separate OR clauses to the timeline, as shown in the screenshot below:
**Expected behavior:**
* The drop area can be resized and scrolled
**Actual behavior:**
* The drag area keeps growing and pushing the table content down
