* Adding event log check to CI check.
* Adding event log check to CI check.
* Can I check out ECS
* Checking out specific ECS branch
* Checking out specific ECS branch
* Custom error message
* Reverting event log mapping test changes
* Pinning to 1.8
* Update .buildkite/scripts/steps/checks/event_log.sh
Co-authored-by: Jonathan Budzenski <jon@budzenski.me>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Jonathan Budzenski <jon@budzenski.me>
* Implement new alert summary widget design and remove chart
* Fix padding issue
* Remove unused translation
* Fix type and test errors
* Fix types and remove extra aggs logic
* Add triggers_actions_ui to storybook list
* Fix small alignment issue by removing extra EuiFlexGroup
* Fix UI issue for small mobile
* Update spacing
Co-authored-by: Kevin Delemme <kdelemme@gmail.com>
Co-authored-by: Kevin Delemme <kdelemme@gmail.com>
Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
* [ftr] add first-class support for playwrite journeys
* [CI] Auto-commit changed files from 'node scripts/generate codeowners'
* fix jest test
* remove ability to customize kibana server args, if we need it we can add it back
* remove dev dir that doesn't exist
* fix typo
* prevent duplicated array converstion logic by sharing flag reader
* remove destructuring of option
* fix scalability config and config_path import
* fix start_servers args and tests
* include simple readme
* fix jest tests and support build re-use when changes are just to jest tests
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
* Fix banner not being displayed on login page
* fix and re-enable banner FTR tests
* revert commit to config file
* add unit test
* don't use whitespace for cli config value
Co-authored-by: Tre <wayne.seymour@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [cft] Remove deployment when a PR is outdated
This changes the stale deployment ttl from 7 days to 2 days
to match the PR outdated check. The longer a deployment is active, the
more likely it is that we'll see a snapshot related break somewhere in
the stack. These are typically template or migration related script
changes.
Longer running deployments can also run out of disk space and start
alerting on health checks.
* day in seconds
* [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix'
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
* [cft] Stabilize deployments
- Switches from general purpose to high memory deployments
- Enables autoscaling
- Allows a warm node to be turned on for longer running deployments with
more data
* fix ml
* revert autoscaling
* fix
* [packages] add kibana.jsonc files
* auto-migrate to kibana.jsonc
* support interactive pkg id selection too
* remove old codeowners entry
* skip codeowners generation when .github/CODEOWNERS doesn't exist
* fall back to format validation if user is offline
* update question style
* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
* add scalability pipeline to run scenarios from APM traces
* update runner description
* remove retry-all-errors curl flag
* add flag for curl to ignore connection refused
* override ES_HOST for gatling runner
* exclude config from regular CI, remove bail flag
* fix uploaded scalability traces
* fix text and remove space
* add validation in config
* use functions instead of scripts
* renaming var in loop
* add step timeout
* define functions before call
* use trap for stopping ES
* fix path for artifacts extraction
* update serverArgs
* add pre-build step
* add pre-build step
* use default pre-build step
* delete step
* print BUILDKITE_PIPELINE_SLUG
* disable telemetry
* remove log
* enable telemetry
* add step to upload test results
* move trap after pid
* upload test reports to gcs
* fix script
* Revert "fix script"
This reverts commit 1c6bc3f45c.
* Revert "upload test reports to gcs"
This reverts commit c957a31c32.
* added storybook config
* first pass of the image component
* use storybook "action" instead of console.log
* fix up some comments and fix if-else statement
* address type exports
* added viewport observer tests
* added files plugin to storybook CI and correct JSON formatting
* ensure that subscription only happens once
* intersectionobserver should always be available
* only run useeffect once
* use React.forwardRef API rather than props
* factor out the viewport observer to a hook
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [cft] Update comment when deployment is available
Currently cloud deployment are linked to after the entire CI run. Cloud
deployments typically finish early, so this provides a notification as
soon as the deployment is available.
* newline
* fix id
* [perf-tests/scalability] improve logging when uploading traces
* restore including kibana artifacts in scalability dataset
* create parent dirs too
* support skipping builds too
* Create test configs for Kibana running dedicated processes
* Fix TS issues
* Fix tests relying on backend responses
* Only run dedicated task process on spaces_and_security suite group2
* Fix ftr_configs
* Use dedicated task runner by default
* fix typo
* Remove exclusive test suite
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
After a deployment is created, a new Kibana plan is automatically added to update settings (to connect APM)
and restart Kibana. Polling for a plan state isn't especially reliable because it flips
between empty and queued, and then empty again depending on how quickly setup is run in cloud.
We want to enable monitoring after the automatic plan has run, if not we get an error:
* deployments.resource_plan_state_error: Kibana resource [main-kibana] has a plan still pending, cancel that or wait for it to complete (settings.observability.plan)
This adds a sleep and retry to see if we can make this step more reliable
* [cft] Add support for creating a new redeployment
- Adds a new label `ci:cloud-redeploy` that will always create a fresh deployment
- Deprecates `ci:deploy-cloud` in favor of namespacing `ci:cloud-deploy`
* booleans
Adds first functional tests for Explain Log Rate Spikes. The test clicks the menu item, selects an index, clicks the "Use full data" button and asserts the page's elements.
