* Add event annotation service structure
* adding annotation layer to lens. passing event annotation service
* simplify initial Dimensions
* add annotations to lens
* no datasource layer
* group the annotations into numerical icons
* color icons in tooltip, add the annotation icon, fix date interval bug
* display old time axis for annotations
* error in annotation dimension when date histogram is removed
* refactor: use the same methods for annotations and reference lines
* wip
* only check activeData for dataLayers
* added new icons for annotations
* refactor icons
* uniqueLabels
* unique Labels
* diff config from args
* change timestamp format
* added expression event_annotation_group
* names refactor
* ea service adding help descriptions
* rotate icon
* added tests
* fix button problem
* dnd problem
* dnd fix
* tests for dimension trigger
* tests for unique labels
* [CI] Auto-commit changed files from 'node scripts/build_plugin_list_docs'
* type
* add new button test
* remove noDatasource from config (only needed when initializing a layer or dimension in getSupportedLayers)
* addressing Joe's and Michael comments
* remove hexagon and square, address Stratoula's feedback
* stroke for icons & icon fill
* fix tests
* fix small things
* align the set with tsvb
* align IconSelect
* fix i18nrc
* Update src/plugins/event_annotation/public/event_annotation_service/index.tsx
Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
* refactor empty button
* CR
* date cr
* remove DimensionEditorSection
* change to emptyShade for traingle fill
* Update x-pack/plugins/lens/public/app_plugin/app.scss
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Alexey Antonov <alexwizp@gmail.com>
resolves https://github.com/elastic/kibana/issues/124366
Adds new task manager configuration keys.
- `xpack.task_manager.event_loop_delay.monitor` - whether to monitor
event loop delay or not; added in case this specific monitoring
causes other issues and we'd want to disable it. We don't know
of any cases where we'd need this today
- `xpack.task_manager.event_loop_delay.warn_threshold` - the number
of milliseconds of event loop delay before logging a warning
This code uses the `perf_hooks.monitorEventLoopDelay()` API[1] to collect
the event loop delay while a task is running.
[1] https://nodejs.org/api/perf_hooks.html#perf_hooksmonitoreventloopdelayoptions
When a significant event loop delay is encountered, it's very likely
that other tasks running at the same time will be affected, and so
will also end up having a long event loop delay value, and warnings
will be logged on those. Over time, though, tasks which have consistently
long event loop delays will outnumber those unfortunate peer tasks, and
be obvious from the volume in the logs.
To make it a bit easier to find these when viewing Kibana logs in Discover,
tags are added to the logged messages to make it easier to find them. One
tag is `event-loop-blocked`, second is the task type, and the third is a string
consisting of the task type and task id.
* Changing structure of minimumScheduleInterval config
* Updating rules client logic to follow enforce flag
* Updating UI to use enforce value
* Updating config key in functional tests
* Fixes
* Fixes
* Updating help text
* Wording suggestsion from PR review
* Log warning instead of throwing an error if rule has default interval less than minimum
* Updating default interval to be minimum if minimum is greater than hardcoded default
* Fixing checks
* Fixing tests
* Fixing tests
* Fixing config
* Fixing checks
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* wip
* wip
* Reverting changes not related to event log aggregation
* Reverting changes not related to event log aggregation
* Updating event log client find to take array of sort options
* Updating tests and adding basic aggregation function
* Adding tests
* Fixing functional test
* Fixing functional test
* Revert "Reverting changes not related to event log aggregation"
This reverts commit 939340e252.
* Revert "Reverting changes not related to event log aggregation"
This reverts commit 40a93a4b3c.
* Getting aggregation and parsing aggregation results
* Cleanup
* Changing api to internal
* Fixing types
* PR feedback
* omg types
* types and optional accessors
* Adding fn to calculate num executions based on date range
* Fleshing out rules client function and tests
* http api
* Cleanup
* Adding schedule delay
* Limit to 1000 logs
* Fixing security tests
* Fixing unit tests
* Validating numExecutions
* Changing sort input format
* Adding more sort fields
* Fixing unit tests
* Adding functional tests
* Adding sort to terms aggregation
* Fixing functional test
* Adding audit event for rule GET
* Adding audit event for rule execution log GET
* PR feedback
* Adding gap policy and using static num buckets
* Fixing checks
* Fixing checks
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* [DOC] Mention CORS is required when external URLs are allowed in Vega
Mention CORS is required when external URLs are allowed in Vega.
* Update docs/user/dashboard/vega-reference.asciidoc
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
* Update docs/user/dashboard/vega-reference.asciidoc
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
* Begin work on building out the backend of an xMatters connector
* Begin work on building out the frontend of an xMatters connector
* Continue attempting to get connector to register properly
* Begin working on the UI for the Edit Connector Test page
* Start working on writing tests for backend component of the xMatters connector
* Remove unneeded test due to not having any fancy escaping
* Write tests for the frontend component of the xMatters connector
* Add documentation for new xMatters connector
* Begin working on functional tests
* Continue work on frontend for xMatters conenctor
* Continue work on backend for xMatters conenctor
* Continue work on the functional tests for the xMatters connector
* Update based on xMatters string reviews
* Remove hidden parameters from ui
* Continue working to get tests running successfully
* Fix my code after rebasing onto latest main
* Fix the xMatters server for the simluator
* Check if listening before listening to the xmatters server in simulator
* Continue work on improving the xMatters connector
* Update strings based on the xMatters team string review
* Remove the headers as an option for the xMatters connector
* Fix alignment of the xmatters logo on the connectors page
* Allow alertId and alertActionGroupName to be null in the xMatters connector for test requests
* Fix the functional tests for the xMatters connector
* Rename alertName to ruleName and remove headers from xMatters connector
* Continue removing headers and renaming alertName to ruleName
* Update the tests so all are passing
* Some clean up for the xMatters connector
* Update the doc images based on changes for the xMatters connector
* Change alert id to use rule id and alert id and be labeled as signal id in the xMatters connector
* Fix failing tests for xMatters connector
* Start addressing comments and failing builds
* Combine if statement
* Update test strings after updating error strings
* Begin making updates after discussions and reviews
* Update failing tests
* Few adjustments after my self review of the xMatters connector
* Fix one failing test
* Fix a few small bugs in the xMatters connector
* Address a few small bugs in the xMatters connector
* Address latest comments and fix a few tests on the xMatters connector
* Adjust naming of secretsUrl and configUrl
* Work on fixing tests for xMatters connector
* Begin updating the xMatters documentation
* Update based on build errors
* Update documentation typo
* Add validation tests for connectors created using the API
* Fix the failing functional tests
* Update docs after review from xMatters team
* Update accidentally duplicated translate id
* Fix small bugs and update based on xMatters team string reviews
* Fix failing tests due to string changes
* [DOCS] Fixes doc build errors
* Update based on comments and feedback
* Update docs based on feedback
* Fix failing functional tests
* Update based on the feedback
* Fix failures in the functional tests
* Remove accidentally added file
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: lcawl <lcawley@elastic.co>
* add back monitoring.ui.metricbeat.index and deprecate
* add back to test
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
With a recent virtualbox update, we're getting failures in CI with:
> The IP address configured for the host-only network is not within the
> allowed ranges. Please update the address used to be within the allowed
> ranges and run the command again.
This updates the IP range used to be compatible.
