* Move formatting columns into response handler
* Use shared csv export
* Cleanup files
* Fix type
* Fix translation
* Filter out non-dimension values
* Add unit tests for tableVisResponseHandler
* Add unit tests for createFormattedTable
* Add unit tests for addPercentageColumn
* Add unit tests for usePagination
* Add unit tests for useUiState
* Add unit tests for table visualization
* Add unit tests for TableVisBasic
* Add unit tests for cell
* Update license
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* first pass
* migrate more plugins
* migrate yet more plugins
* more oss plugins
* fix test file
* change Plugin signature on the client-side too
* fix test types
* migrate OSS client-side plugins
* migrate OSS client-side test plugins
* migrate xpack client-side plugins
* revert fix attempt on fleet plugin
* fix presentation start signature
* fix yet another signature
* add warnings for server-side async plugins in dev mode
* remove unused import
* fix isPromise
* Add client-side deprecations
* update migration examples
* update generated doc
* fix xpack unit tests
* nit
* (will be reverted) explicitly await for license to be ready in the auth hook
* Revert "(will be reverted) explicitly await for license to be ready in the auth hook"
This reverts commit fdf73feb
* restore await on on promise contracts
* Revert "(will be reverted) explicitly await for license to be ready in the auth hook"
This reverts commit fdf73feb
* Revert "restore await on on promise contracts"
This reverts commit c5f2fe51
* add delay before starting tests in FTR
* update deprecation ts doc
* add explicit contract for monitoring setup
* migrate monitoring plugin to sync
* change plugin timeout to 10sec
* use delay instead of silence
resolves https://github.com/elastic/kibana/issues/88333
Fixed:
- add note that `secure: false` will use TLS, but after an initial connection
with TCP; we have been getting questions from customers who believed that
`secure: false` implied TLS was not used at all.
- added a link to the nodemailer "well-known services" module, to allow
customers to see examples of other email service configurations
- updated the Outlook config example to use the current nodemailer values
- couple of other small tweaks
* Revert "Revert "Migrations v2: don't auto-create indices + FTR/esArchiver support (#85778)""
This reverts commit f97958043f.
* Fix flaky saved objects management test #89953
* If a clone target exists, wait for yellow, not green, index status
* Fix test after master merge
* Fix types
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Search Sessions: Unskip Flaky Functional Test
* Save all search sessions and then manage them based on their persisted state
* Get default search session expiration from config
* randomize sleep time
* fix test
* fix test
* Make sure we poll, and dont persist, searches not in the context of a session
* Added keepalive unit tests
* fix ts
* code review @lukasolson
* ts
* More tests, rename onScreenTimeout to completedTimeout
* lint
* lint
* Delete async seaches
* Support saved object pagination
Fix get search status tests
* better PersistedSearchSessionSavedObjectAttributes ts
* test titles
* Remove runAt from monitoring task
Increase testing trackingInterval (caused bug)
* support workload histograms that take into account overdue tasks
* Update touched when changing session status to complete \ error
* removed test
* Updated management test data
* Rename configs
* delete tap first
add comments
* Use sync config in data-enhanced plugin
* fix merge
* fix merge
* ts
* code review
Co-authored-by: Timothy Sullivan <tsullivan@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Anton Dosov <anton.dosov@elastic.co>
Co-authored-by: Gidi Meir Morris <github@gidi.io>
* chore(NA): simple changes on bazelrc
* chore(NA): integrate bazel tools with BuildBuddy and remote cache service
* chore(NA) fix bazelrc line config
* chore(NA): move non auth settings out of bazelrc.auth
* chore(NA): output home dir
* chore(NA): load .bazelrc-ci.auth from /Users/tiagocosta dir
* chore(NA): remove bazelrc auth file and append directly into home bazelrc
* chore(NA): comment announce option
* chore(NA): integrate build buddy metadata
* chore(NA): update src/dev/ci_setup/.bazelrc-ci
Co-authored-by: Tyler Smalley <tylersmalley@me.com>
* chore(NA): move build metadata integation to common confdig
* chore(NA): fix problem on bazel file location
* chore(NA): correct sh file permissions
* chore(NA): only get host on CI
* chore(NA): add cores into host info on CI
* chore(NA): sync with last settings to setup bazelisk tools on ci
* chore(NA): sync last changes on ci setup env
* chore(NA): sync settings on ci setup with the other PR
* chore(NA): remove yarn export
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tyler Smalley <tylersmalley@me.com>
* Convert user values back to string after yaml template compilation if they were strings originally
* Add better test cases and adjust patch
* Fix when field is undefined
* Handle array of strings too
* chore(NA): build bazel projects all at once in the distributable build process
* chore(NA): make sure bazelisk is installed
* chore(NA): install bazelisk using npm
* chore(NA): remove extra spac
* chore(NA): test yarn path exports
* chore(NA): add direct global dir
* chore(NA): some more debug steps
* chore(NA): remove one statement
* chore(NA): comment one more line out for testing purposes
* chore(NA): export the correct yarn bin location into the PATH
* chore(NA): cleaning implementation
* chore(NA): move installation process of bazelisk into npm
* chore(NA): add missing type
## [Security Solution] [Timeline] Endpoint row renderers (1st batch)
This PR implements the 1st batch of Endpoint (`event.module: "endpoint"`) row renderers by updating and enhancing some of the existing "Endgame" (`event.module: "endgame"`) row renderers to use the latest [ECS fields](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html).
The following Endpoint events will be rendered via row renderers in Timeline:
| event.dataset | event.action |
|--------------------------|---------------------|
| endpoint.events.file | creation |
| endpoint.events.file | deletion |
| endpoint.events.process | start |
| endpoint.events.process | end |
| endpoint.events.network | lookup_requested |
| endpoint.events.network | lookup_result |
| endpoint.events.network | connection_accepted |
| endpoint.events.network | disconnect_received |
| endpoint.events.security | log_on |
| endpoint.events.security | log_off |
## File (FIM) Creation events
Endpoint File (FIM) Creation events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.file and event.action: creation
```
### Sample rendered File (FIM) Creation event
Each field with `this formatting` is draggable (to pivot a search) in the row-rendered event:
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` created a file `WimProvider.dll` in `C:\Windows\TEMP\F590BACBAE94\WimProvider.dll` via `MsMpEng.exe` `(2424)`
### Fields in a File (FIM) Creation event
`user.name` \ `user.domain` @ `host.name` created a file `file.name` in `file.path` via `process.name` `(process.pid)`
## File (FIM) Deletion events
Endpoint File (FIM) Deletion events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.file and event.action: deletion
```
### Sample rendered File (FIM) Deletion event
`SYSTEM` \ `NT AUTHORITY` @ `windows-endpoint-1` deleted a file `AM_Delta_Patch_1.329.2793.0.exe` in `C:\Windows\SoftwareDistribution\Download\Install\AM_Delta_Patch_1.329.2793.0.exe` via `svchost.exe` `(1728)`
### Fields in a File (FIM) Deletion event
`user.name` \ `user.domain` @ `host.name` deleted a file `file.name` in `file.path` via `process.name` `(process.pid)`
## Process Start events
Endpoint Process Start events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.process and event.action: start
```
### Sample rendered Process Start event
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` started process `conhost.exe` (`376`) `C:\Windows\system32\conhost.exe` `0xffffffff` `-ForceV1` via parent process `sshd.exe` (`6460`)
`sha256 697334c236cce7d4c9e223146ee683a1219adced9729d4ae771fd6a1502a6b63`
`sha1 e19da2c35ba1c38adf12d1a472c1fcf1f1a811a7`
`md5 1b0e9b5fcb62de0787235ecca560b610`
### Fields in a Process Start event
The following fields will be used to render a Process Start event:
`user.name` \ `user.domain` @ `host.name` started process `process.name` (`process.pid`) `process.args` via parent process `process.parent.name` (`process.parent.pid`)
`process.hash.sha256`
`process.hash.sha1`
`process.hash.md5`
## Process End events
Endpoint Process End events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.process and event.action: end
```
### Sample rendered Process End event
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` terminated process `svchost.exe` (`10392`) `C:\Windows\System32\svchost.exe` `-k` `netsvcs` `-p` `-s` `NetSetupSvc` with exit code `0` via parent process `services.exe` `(568)`
`7fd065bac18c5278777ae44908101cdfed72d26fa741367f0ad4d02020787ab6`
`a1385ce20ad79f55df235effd9780c31442aa234`
`8a0a29438052faed8a2532da50455756`
### Fields in a Process End event
The following fields will be used to render a Process End event:
`user.name` \ `user.domain` @ `host.name` terminated process `process.name` (`process.pid`) with exit code `process.exit_code` via parent process `process.parent.name` (`process.parent.pid`)
`process.hash.sha256`
`process.hash.sha1`
`process.hash.md5`
## Network (DNS) Lookup Requested events
Endpoint Network (DNS) Lookup Requested events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.network and event.action: lookup_requested
```
### Runtime matching criteria
All Network Lookup Requested events, including Endpoint and non-Endpoint DNS events matching the following criteria will be rendered:
```
dns.question.type: * and dns.question.name: *
```
### Sample rendered Network Lookup Requested event
`SYSTEM` \ `NT AUTHORITY` @ `windows-endpoint-1` asked for `logging.googleapis.com` with question type `A` via `google_osconfig_agent.exe` `(4064)` `dns`
### Fields in a Network Lookup Requested event
The following fields will be used to render a Network Lookup Request event:
`user.name` \ `user.domain` @ `host.name` asked for `dns.question.name` with question type `dns.question.type` via `process.name` `(process.pid)` `network.protocol`
## Network Lookup Result events
Endpoint Network (DNS) Lookup Result events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.network and event.action: lookup_result
```
### Runtime matching criteria
All Network Lookup Result events, including Endpoint and non-Endpoint DNS events matching the following criteria will be rendered:
```
dns.question.type: * and dns.question.name: *
```
### Sample rendered Network Lookup Result event
`SYSTEM` \ `NT AUTHORITY` @ `windows-endpoint-1` asked for `logging.googleapis.com` with question type `AAAA` via `GCEWindowsAgent.exe` `(684)` `dns`
### Fields in a Network Lookup Result event
The following fields will be used to render a Network Lookup Result event:
`user.name` \ `user.domain` @ `host.name` asked for `dns.question.name` with question type `dns.question.type` via `process.name` `(process.pid)` `network.protocol`
## Network Connection Accepted events
Endpoint Network Connection Accepted events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.network and event.action: connection_accepted
````
### Sample rendered Network Connection Accepted event
Network Connection Accepted events, like the one in the screenshot above, are also rendered by the _Netflow_ row renderer, which displays information that includes the directionality of the connection, protocol, and source / destination details.
`NETWORK SERVICE` \ `NT AUTHORITY` @ `windows-endpoint-1` accepted a connection via `svchost.exe` `(328)` with result `success`
### Fields in a Network Connection Accepted event
`user.name` \ `user.domain` @ `host.name` accepted a connection via `process.name` `(process.pid)` with result `event.outcome`
## Network Disconnect Received events
Endpoint Network Disconnect Received events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.network and event.action: disconnect_received
````
### Sample rendered Network Disconnect Received event
Network Disconnect Received events, like the one in the screenshot above, are also rendered by the _Netflow_ row renderer, which displays information that includes the directionality of the connection, protocol, and source / destination details.
`NETWORK SERVICE` \ `NT AUTHORITY` @ `windows-endpoint-1` disconnected via `svchost.exe` `(328)`
### Fields in a Network Disconnect Received event
`user.name` \ `user.domain` @ `host.name` disconnected via `process.name` `(process.pid)`
## Security Log On events
Endpoint Security Log On events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.security and event.action: log_on
```
### `event.outcome: "success"` vs `event.outcome: "failure"`
The row renderer for Security Log On events uses the `event.outcome` field to display different results for events matching:
```
event.dataset: endpoint.events.security and event.action: log_on and event.outcome: success
```
vs events matching:
```
event.dataset: endpoint.events.security and event.action: log_on and event.outcome: failure
```
### Sample rendered Security Log On / `event.outcome: "success"` event
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` successfully logged in via `C:\Program Files\OpenSSH-Win64\sshd.exe`
### Fields in an Security Log On / `event.outcome: "success"` event
`user.name` \ `user.domain` @ `host.name` successfully logged in via `process.name` (`process.pid`)
### Sample rendered Security Log On / `event.outcome: "failure"` event
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` failed to log in via `C:\Program Files\OpenSSH-Win64\sshd.exe`
### Fields in an Security Log On / `event.outcome: "failure"` event
`user.name` \ `user.domain` @ `host.name` failed to log in via `process.name` (`process.pid`)
## Security Log Off events
Endpoint Security Log Off events with the following `event.dataset` and `event.action` will be rendered in Timeline via row renderers:
```
event.dataset: endpoint.events.security and event.action: log_off
```
### Sample rendered Security Log Off event
`SYSTEM` \ `NT AUTHORITY` @ `win2019-endpoint` logged off via `C:\Program Files\OpenSSH-Win64\sshd.exe`
### Fields in a Security Log Off event
`user.name` \ `user.domain` @ `host.name` logged off via `process.name` (`process.pid`)
* Add eslint rule for linting unnecessary backticks
This needs to be below the Prettier overrides at the bottom of the file to override Prettier
* Run --fix
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [Setup] Split rule that explicitly allows `any` in test/mock files into its own section
- so that the rules we're about to add apply correctly to all files
* Add react/jsx-boolean-value rule
* Run --fix
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
